Triple
T11579253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oghene |
E274581
|
entity |
| Predicate | intermediaries |
P51073
|
FINISHED |
| Object | lesser deities |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: lesser deities | Statement: [Oghene, intermediaries, lesser deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intermediaries Context triple: [Oghene, intermediaries, lesser deities]
-
A.
intermediaryType
Indicates the specific role or category of intermediary involved in facilitating the relationship or transaction between entities.
-
B.
mediatedBetween
Indicates that an entity acted as an intermediary or go-between facilitating interaction, communication, or negotiation between two other entities.
-
C.
intermediateTerminus
Indicates that something serves as a temporary or middle stopping point within a larger route, process, or sequence.
-
D.
mediatedIn
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
E.
intercessorFor
chosen
Indicates that one entity acts as a mediator or advocate on behalf of another entity, typically intervening or pleading for them with a third party.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904b46288190890ecafd6ceb0c3d |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.