Triple
T14796880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakyiri |
E347803
|
entity |
| Predicate | typeOfAncestry |
P116143
|
FINISHED |
| Object | shared mythical or historical ancestor |
—
|
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: shared mythical or historical ancestor | Statement: [Asakyiri, typeOfAncestry, shared mythical or historical ancestor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAncestry Context triple: [Asakyiri, typeOfAncestry, shared mythical or historical ancestor]
-
A.
typeOfAncestor
Indicates that one entity is an ancestor (of any generational distance) of another entity.
-
B.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
C.
typicalAncestryDescription
Indicates the usual or most common ancestral background associated with an entity.
-
D.
typeOfInheritance
Indicates the kind or pattern of inheritance by which a trait, property, or characteristic is passed from one entity or generation to another.
-
E.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.