Triple
T23704600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menelik I |
E585682
|
entity |
| Predicate | lineageClaimedBy |
P115355
|
FINISHED |
| Object | Haile Selassie I |
—
|
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: Haile Selassie I | Statement: [Menelik I, lineageClaimedBy, Haile Selassie I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageClaimedBy Context triple: [Menelik I, lineageClaimedBy, Haile Selassie I]
-
A.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
B.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
C.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
D.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b685dfc8819081906aceab7b0bdd |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.