Triple
T30714384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ulaş |
E781981
|
entity |
| Predicate | hasSultan |
P140617
|
FINISHED |
| Object | Mustafa II |
—
|
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: Mustafa II | Statement: [Battle of Ulaş, hasSultan, Mustafa II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSultan Context triple: [Battle of Ulaş, hasSultan, Mustafa II]
-
A.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
B.
associatedSultan
chosen
Indicates that one entity is linked or connected to a particular sultan in some relevant context or relationship.
-
C.
reignAsValideSultanFor
Indicates that one entity serves and exercises authority as the valide sultan (queen mother) during the reign of another entity, typically a ruling sultan.
-
D.
hasSultanLoge
Indicates that an entity possesses or includes a special seating area designated as the sultan’s box or royal loge.
-
E.
currentSultanRole
Indicates that an entity currently holds the role or position of sultan.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:35 p.m.