Triple
T37889200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekwefi |
E945078
|
entity |
| Predicate | survivingChild |
P189581
|
FINISHED |
| Object | Ezinma |
—
|
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: Ezinma | Statement: [Ekwefi, survivingChild, Ezinma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingChild Context triple: [Ekwefi, survivingChild, Ezinma]
-
A.
survivingChildOfParents
Indicates that one entity is a child who remains alive after the death of the specified parent or parents.
-
B.
onlySurvivingChildOf
Indicates that one person is the sole remaining living child of another person, with no other surviving siblings.
-
C.
numberOfChildrenSurvivors
Indicates the count of children who survived a particular event, condition, or situation.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivedBy
Indicates that one entity continues to live or exist after the death or end of another entity.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.