Triple
T2429120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Heraclea |
E52800
|
entity |
| Predicate | commandingSide |
P15834
|
FINISHED |
| Object | Pyrrhus of Epirus on the Epirote side |
—
|
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: Pyrrhus of Epirus on the Epirote side | Statement: [Battle of Heraclea, commandingSide, Pyrrhus of Epirus on the Epirote side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandingSide Context triple: [Battle of Heraclea, commandingSide, Pyrrhus of Epirus on the Epirote side]
-
A.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
B.
commandersSide
chosen
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
C.
opposingCommander
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.
-
D.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.