Triple
T33085535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Shewa |
E846627
|
entity |
| Predicate | earlierRuler |
P182864
|
FINISHED |
| Object | Negus Sahle Selassie of Shewa |
—
|
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: Negus Sahle Selassie of Shewa | Statement: [House of Shewa, earlierRuler, Negus Sahle Selassie of Shewa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierRuler Context triple: [House of Shewa, earlierRuler, Negus Sahle Selassie of Shewa]
-
A.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
B.
beganWithRuler
Indicates that an event, period, or sequence started under the authority or reign of a specified ruler.
-
C.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
D.
currentRuler
Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 1, 2026, 1:26 a.m.