Triple
T14715678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heraklion International Airport |
E345672
|
entity |
| Predicate | isBusySeason |
P15928
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Heraklion International Airport, isBusySeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusySeason Context triple: [Heraklion International Airport, isBusySeason, summer]
-
A.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
-
B.
hasSeasonalStatus
chosen
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
C.
sportSeasonOf
Indicates that one entity is a sports season that belongs to, or is part of, the overall history or schedule of the specified sport.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.