Triple
T34823225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emir of Hadejia |
E1003845
|
entity |
| Predicate | highestRankingRulerOf |
P60298
|
FINISHED |
| Object | Hadejia Emirate |
—
|
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: Hadejia Emirate | Statement: [Emir of Hadejia, highestRankingRulerOf, Hadejia Emirate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestRankingRulerOf Context triple: [Emir of Hadejia, highestRankingRulerOf, Hadejia Emirate]
-
A.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
D.
rulerOf
chosen
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
E.
lastMonarchOf
Indicates that one entity is the final reigning monarch of another entity, such as a country, kingdom, or territory.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4 p.m.