Triple
T29786772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oyoko dynasty |
E756285
|
entity |
| Predicate | providesTitleHoldersFor |
P192840
|
FINISHED |
| Object | Asantehene |
—
|
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: Asantehene | Statement: [Oyoko dynasty, providesTitleHoldersFor, Asantehene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesTitleHoldersFor Context triple: [Oyoko dynasty, providesTitleHoldersFor, Asantehene]
-
A.
titleHolders
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
B.
includedTitleHolder
Indicates that an entity is recognized or recorded as holding a specified title within a given context or collection.
-
C.
titleHoldersReceive
Indicates that designated title holders are the recipients of something, such as rights, benefits, or responsibilities, associated with that title.
-
D.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
E.
titleHoldersLinkedTo
Indicates that two or more entities are connected through holding, sharing, or transferring the same title or position.
- F. None of above. chosen
Provenance (4 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: April 29, 2026, 5:09 p.m.