Triple
T29466092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buyid family |
E747382
|
entity |
| Predicate | ruledInNameOf |
P87999
|
FINISHED |
| Object | Abbasid caliphs |
—
|
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: Abbasid caliphs | Statement: [Buyid family, ruledInNameOf, Abbasid caliphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledInNameOf Context triple: [Buyid family, ruledInNameOf, Abbasid caliphs]
-
A.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
B.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
D.
ruledInPlaceOf
Indicates that one entity exercised governing authority or leadership as a substitute or proxy for another entity.
-
E.
ruledDuringReignOf
chosen
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ba7afcc8190a98cfe4f88ab7bc7 |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:53 p.m.