Triple
T3845896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phocian League |
E93567
|
entity |
| Predicate | outcomeOfThirdSacredWar |
P44060
|
FINISHED |
| Object | defeat by Philip II of Macedon |
—
|
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: defeat by Philip II of Macedon | Statement: [Phocian League, outcomeOfThirdSacredWar, defeat by Philip II of Macedon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeOfThirdSacredWar Context triple: [Phocian League, outcomeOfThirdSacredWar, defeat by Philip II of Macedon]
-
A.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
resultOfSixthCrusade
Indicates that something occurs as a consequence or outcome of the events or agreements associated with the Sixth Crusade.
-
C.
aimOfPhilipV
Indicates that something is the goal, intention, or objective pursued by Philip V.
-
D.
opponentAtBattleOfTheNile
Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
-
E.
partOfConflictOutcome
chosen
Indicates that one entity represents a specific component or aspect of the overall outcome of a conflict involving another entity.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb77a488190be7fc2a1211f1f2d |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.