Triple
T36617140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vizier of the Seljuk Empire |
E903633
|
entity |
| Predicate | chiefAdvisorTo |
P36354
|
FINISHED |
| Object | Sultan of the Seljuk Empire |
—
|
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: Sultan of the Seljuk Empire | Statement: [Vizier of the Seljuk Empire, chiefAdvisorTo, Sultan of the Seljuk Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefAdvisorTo Context triple: [Vizier of the Seljuk Empire, chiefAdvisorTo, Sultan of the Seljuk Empire]
-
A.
chiefStrategist
Indicates that one entity serves as the primary planner and director of strategy for another entity.
-
B.
chiefSaintOf
Indicates that one entity serves as the principal or primary patron saint associated with another entity (such as a place, group, or institution).
-
C.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
D.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
E.
advisorOf
chosen
Indicates that one entity serves as an advisor, providing guidance or counsel, to another entity.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.