Triple
T24426873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Malazgirt |
E615883
|
entity |
| Predicate | SeljukArmyComposition |
P6154
|
FINISHED |
| Object | mounted archers |
—
|
LITERAL FINISHED |
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: mounted archers | Statement: [Battle of Malazgirt, SeljukArmyComposition, mounted archers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SeljukArmyComposition Context triple: [Battle of Malazgirt, SeljukArmyComposition, mounted archers]
-
A.
primarySeljukForces
Indicates that the referenced forces constitute the main or principal military contingent of the Seljuk side in a given context or conflict.
-
B.
commanderSeljuk
Indicates that one entity served as a military commander within the Seljuk context (e.g., army, campaign, or polity) for the other entity.
-
C.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
OttomanForcesIncluded
Indicates that the composition of a military force or contingent included units or personnel from the Ottoman forces.
-
E.
servedArmy
Indicates that an entity has performed military service in, or been a member of, a particular army.
- 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.