Triple
T8473642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ecnomus |
E200337
|
entity |
| Predicate | fleetSizeRome |
P1848
|
FINISHED |
| Object | approximately 330 warships |
—
|
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: approximately 330 warships | Statement: [Battle of Ecnomus, fleetSizeRome, approximately 330 warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetSizeRome Context triple: [Battle of Ecnomus, fleetSizeRome, approximately 330 warships]
-
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.
fleetSize
chosen
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
C.
ImperialLeagueForcesStrength
Indicates the level or magnitude of military power possessed by the Imperial League’s forces.
-
D.
aimOfRome
Indicates that something is the goal, purpose, or intended objective of Rome.
-
E.
estimatedCarthaginianForces
Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f7328481909ad19bcf8d182022 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.