Triple
T28398569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bridge |
E719343
|
entity |
| Predicate | SasanianCavalryComponent |
P46576
|
FINISHED |
| Object | Savaran heavy cavalry |
—
|
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: Savaran heavy cavalry | Statement: [Battle of the Bridge, SasanianCavalryComponent, Savaran heavy cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SasanianCavalryComponent Context triple: [Battle of the Bridge, SasanianCavalryComponent, Savaran heavy cavalry]
-
A.
SasanianForcesStrength
Indicates the level or magnitude of military power or troop numbers possessed by Sasanian forces in a given context.
-
B.
sideSasanian
Indicates that an entity is aligned with, belongs to, or is on the side of the Sasanian faction or polity in a given context.
-
C.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
D.
PersianForceComponent
chosen
Indicates that an entity functions as a constituent unit or sub-force within a larger Persian military force or formation.
-
E.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:18 a.m.