Triple
T11199275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Carrhae |
E264996
|
entity |
| Predicate | ParthianCasualties |
P82956
|
FINISHED |
| Object | light |
—
|
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: light | Statement: [Battle of Carrhae, ParthianCasualties, light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ParthianCasualties Context triple: [Battle of Carrhae, ParthianCasualties, light]
-
A.
RomanLegionsDestroyed
Indicates that one or more Roman legions were annihilated or decisively defeated, typically resulting in their destruction as effective military units.
-
B.
CarthaginianLosses
Indicates the number or extent of losses suffered by the Carthaginians in a given conflict or event.
-
C.
secondDacianWar
Indicates that an entity participates in, is associated with, or is relevant to the historical event known as the Second Dacian War.
-
D.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
E.
militaryCasualtiesSide
chosen
Indicates the side or party in a conflict to which the recorded military casualties belong.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.