Triple
T34951532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aro Confederacy |
E1008011
|
entity |
| Predicate | usedInstrumentOfPower |
P933
|
FINISHED |
| Object | Ibini Ukpabi oracle |
—
|
NE NERFINISHED |
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: Ibini Ukpabi oracle | Statement: [Aro Confederacy, usedInstrumentOfPower, Ibini Ukpabi oracle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInstrumentOfPower Context triple: [Aro Confederacy, usedInstrumentOfPower, Ibini Ukpabi oracle]
-
A.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
B.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
D.
usesInstrument
chosen
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 3, 2026, 4 p.m.