Triple
T14377688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midsummer in Leksand |
E356516
|
entity |
| Predicate | celebratedInSeason |
P3473
|
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: [Midsummer in Leksand, celebratedInSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebratedInSeason Context triple: [Midsummer in Leksand, celebratedInSeason, summer]
-
A.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
B.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
C.
celebratedDuring
chosen
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
D.
notableSeasonAsOC
Indicates that an individual had a particularly significant or noteworthy season while serving as an offensive coordinator.
-
E.
celebratedAt
Indicates that an event, occasion, or achievement is celebrated or observed at a particular place or time.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.