Triple
T8473648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ecnomus |
E200337
|
entity |
| Predicate | casualtiesCarthage |
P1399
|
FINISHED |
| Object | heavy ship losses |
—
|
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: heavy ship losses | Statement: [Battle of Ecnomus, casualtiesCarthage, heavy ship losses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesCarthage Context triple: [Battle of Ecnomus, casualtiesCarthage, heavy ship losses]
-
A.
estimatedCarthaginianForces
Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
-
B.
casualtiesAtTobruk
Indicates that an entity experienced casualties (killed, wounded, or missing) in connection with the events at Tobruk.
-
C.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
E.
CarthaginianCommander
Indicates that the subject serves as a military commander for Carthage or is identified as holding a commanding role within the Carthaginian forces.
- 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.