Triple
T28908615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Utica (203 BC) |
E733154
|
entity |
| Predicate | NumidianCommander |
P165519
|
FINISHED |
| Object | Syphax |
—
|
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: Syphax | Statement: [Battle of Utica (203 BC), NumidianCommander, Syphax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NumidianCommander Context triple: [Battle of Utica (203 BC), NumidianCommander, Syphax]
-
A.
CarthaginianCommander
Indicates that the subject serves as a military commander for Carthage or is identified as holding a commanding role within the Carthaginian forces.
-
B.
RomanCommander
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
C.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
D.
ArgiveCommander
Indicates a relationship where an entity holds the role or status of a commander associated with Argos or the Argives.
-
E.
commanderOfVisigothicForces
Indicates that one entity serves as the military commander of the Visigothic forces in a given context or conflict.
- F. None of above. chosen
Provenance (4 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65adcd92481909cbd80dd57623e82 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 8:09 a.m.