Triple
T34604125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metaurus |
E888547
|
entity |
| Predicate | battleCommanderCarthaginian |
P48697
|
FINISHED |
| Object | Hasdrubal Barca |
—
|
NE NERFINISHED |
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: Hasdrubal Barca | Statement: [Metaurus, battleCommanderCarthaginian, Hasdrubal Barca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCommanderCarthaginian Context triple: [Metaurus, battleCommanderCarthaginian, Hasdrubal Barca]
-
A.
CarthaginianCommander
chosen
Indicates that the subject serves as a military commander for Carthage or is identified as holding a commanding role within the Carthaginian forces.
-
B.
CarthaginianForceType
Indicates the type or classification of a Carthaginian military force involved in a given context or event.
-
C.
estimatedCarthaginianForces
Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
-
D.
NumidianCommander
Indicates that an entity serves as a military commander associated with Numidia or Numidian forces.
-
E.
SamniteCommander
Indicates that one entity serves as a military commander or leader within the Samnite forces 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.