Triple
T15460818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonnatus |
E371892
|
entity |
| Predicate | roleInLamianWar |
P108011
|
FINISHED |
| Object | Macedonian commander against Greek rebels |
—
|
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: Macedonian commander against Greek rebels | Statement: [Leonnatus, roleInLamianWar, Macedonian commander against Greek rebels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLamianWar Context triple: [Leonnatus, roleInLamianWar, Macedonian commander against Greek rebels]
-
A.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
-
B.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
C.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
E.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.