Triple
T18969194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onomarchus of Phocis |
E464121
|
entity |
| Predicate | roleInThirdSacredWar |
P28183
|
FINISHED |
| Object | principal Phocian commander |
—
|
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: principal Phocian commander | Statement: [Onomarchus of Phocis, roleInThirdSacredWar, principal Phocian commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInThirdSacredWar Context triple: [Onomarchus of Phocis, roleInThirdSacredWar, principal Phocian commander]
-
A.
takesSideInTrojanWar
Indicates that an entity participates in the Trojan War as a supporter of one of the opposing sides.
-
B.
roleInPunicWars
Indicates the specific involvement, function, or position an entity had in the events or campaigns of the Punic Wars.
-
C.
ArgiveCommander
Indicates a relationship where an entity holds the role or status of a commander associated with Argos or the Argives.
-
D.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
roleInBattleOfMetaurus
Indicates the specific role or involvement an entity had in the Battle of the Metaurus.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d618e2ec8190848a41733e6db2f1 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon