Triple
T24426856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Malazgirt |
E615883
|
entity |
| Predicate | SeljukSultanAtTime |
P82015
|
FINISHED |
| Object | Alp Arslan |
—
|
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: Alp Arslan | Statement: [Battle of Malazgirt, SeljukSultanAtTime, Alp Arslan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SeljukSultanAtTime Context triple: [Battle of Malazgirt, SeljukSultanAtTime, Alp Arslan]
-
A.
المالك
Indicates a relationship where one entity is the owner or possessor of another entity.
-
B.
recognizedAsSultan
chosen
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
C.
startOfReignAsGreatSeljukSultan
Indicates the point in time when an individual begins their rule as the Great Seljuk Sultan.
-
D.
commanderSeljuk
Indicates that one entity served as a military commander within the Seljuk context (e.g., army, campaign, or polity) for the other entity.
-
E.
predecessorAsValideSultan
Indicates that one entity served as the immediately preceding legitimate sultan 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a84c848190bce2c004a667dbe7 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.