Triple
T23856848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masud I of Rum |
E592331
|
entity |
| Predicate | dynasticRealm |
P83925
|
FINISHED |
| Object | Seljuk Sultanate of Rum |
—
|
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: Seljuk Sultanate of Rum | Statement: [Masud I of Rum, dynasticRealm, Seljuk Sultanate of Rum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticRealm Context triple: [Masud I of Rum, dynasticRealm, Seljuk Sultanate of Rum]
-
A.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
B.
dynasticState
chosen
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
C.
dynasticScope
Indicates the range or extent of influence, authority, or relevance associated with a particular dynasty or dynastic period.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98bf1d081908279fc145371afa5 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:12 p.m.