Triple
T30162134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cabira |
E766695
|
entity |
| Predicate | hasCommanderForPontus |
P1197
|
FINISHED |
| Object | Mithridates VI of Pontus |
—
|
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: Mithridates VI of Pontus | Statement: [Battle of Cabira, hasCommanderForPontus, Mithridates VI of Pontus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForPontus Context triple: [Battle of Cabira, hasCommanderForPontus, Mithridates VI of Pontus]
-
A.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
PonticCommander
Indicates a person who holds a commanding military role within the forces of Pontus or a Pontic polity.
-
D.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
E.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0116ca6a1c81909a9e938dbe54eb8a |
completed | May 10, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_6a0116655e248190bdfe5b4bb4f1cf47 |
completed | May 10, 2026, 11:36 p.m. |
Created at: April 29, 2026, 7:22 p.m.