Triple
T30198405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Cyzicus |
E767696
|
entity |
| Predicate | commandedByOnPonticSide |
P1407
|
FINISHED |
| Object | Mithridates VI Eupator |
—
|
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 Eupator | Statement: [Siege of Cyzicus, commandedByOnPonticSide, Mithridates VI Eupator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedByOnPonticSide Context triple: [Siege of Cyzicus, commandedByOnPonticSide, Mithridates VI Eupator]
-
A.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
B.
commandedSide
Indicates that one entity served as the commanding side or force in relation to another entity, typically within a conflict, operation, or hierarchical command structure.
-
C.
commandedBy
chosen
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commandedByFrom
Indicates that an entity is under the authority or control of another entity originating from a specified source or location.
-
E.
commandeeredBy
Indicates that control or possession of something has been forcibly taken over by a particular agent or group.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 7:30 p.m.