Triple
T6754108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Myriokephalon |
E154409
|
entity |
| Predicate | primarySeljukForces |
P73301
|
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 Myriokephalon, primarySeljukForces, mounted archers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySeljukForces Context triple: [Battle of Myriokephalon, primarySeljukForces, mounted archers]
-
A.
primaryTacticOttomans
Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
-
B.
OttomanCommander
Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
-
C.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
D.
sultanDuringConflict
Indicates that an individual holds the position or role of sultan during a specific conflict or period of armed struggle.
-
E.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
- F. None of above. chosen
Provenance (4 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:11 p.m.