Triple
T32547504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herdonia |
E831884
|
entity |
| Predicate | opponentCommanderAtBattle |
P1698
|
FINISHED |
| Object | Hannibal 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: Hannibal Barca | Statement: [Herdonia, opponentCommanderAtBattle, Hannibal Barca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentCommanderAtBattle Context triple: [Herdonia, opponentCommanderAtBattle, Hannibal Barca]
-
A.
opponentCommanderAttacker
Indicates that the referenced commander is the opposing side’s commander who is initiating or carrying out an attack.
-
B.
opposingCommander
chosen
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
C.
opponentCommanderSide
Indicates that one commander is positioned on the opposing side relative to another commander in a conflict or competitive scenario.
-
D.
opposingCommanderSide
Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
-
E.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:02 a.m.