Triple
T21807170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bagradas River (255 BCE) |
E538378
|
entity |
| Predicate | hasRomanForceComponent |
P86507
|
FINISHED |
| Object | legionary infantry |
—
|
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: legionary infantry | Statement: [Battle of the Bagradas River (255 BCE), hasRomanForceComponent, legionary infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanForceComponent Context triple: [Battle of the Bagradas River (255 BCE), hasRomanForceComponent, legionary infantry]
-
A.
estimatedRomanForces
Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
-
B.
hasRomanRemains
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
C.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
D.
ParthianForceType
Indicates the type or classification of a military force associated with the Parthians.
-
E.
RomanLegionsPresent
chosen
Indicates that Roman military legions are present at or within the specified location or context.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.