Triple
T3218152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mycale |
E67444
|
entity |
| Predicate | impactOnGreece |
P4749
|
FINISHED |
| Object | facilitated formation of the Delian League |
—
|
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: facilitated formation of the Delian League | Statement: [Battle of Mycale, impactOnGreece, facilitated formation of the Delian League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnGreece Context triple: [Battle of Mycale, impactOnGreece, facilitated formation of the Delian League]
-
A.
impactOnConstantinople
Indicates a relationship where one entity has an effect, influence, or consequence specifically on the city of Constantinople.
-
B.
impactOnIran
Indicates the effect or consequences that an action, event, or policy has on Iran.
-
C.
historicalImpact
chosen
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
D.
effectOnSpain
Indicates a relationship where one entity produces an influence, change, or consequence specifically affecting Spain.
-
E.
adoptedAsNationalAnthemInGreece
Indicates that a work was officially adopted as the national anthem by the state of Greece.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0c48b481909d1bd9dc41dfa8c2 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.