Triple
T13402368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savour the Games |
E319862
|
entity |
| Predicate | olympicSeason |
P108847
|
FINISHED |
| Object | Winter |
—
|
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: Winter | Statement: [Savour the Games, olympicSeason, Winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olympicSeason Context triple: [Savour the Games, olympicSeason, Winter]
-
A.
OlympicSeason
chosen
Indicates the specific Olympic Games edition or seasonal cycle (e.g., Summer or Winter) during which the related event, performance, or participation took place.
-
B.
olympicGames
Indicates that an entity is an edition or instance of the Olympic Games event.
-
C.
sequenceInSummerOlympics
Indicates that one event, competition, or occurrence takes place in a specific order or position within the sequence of events at the Summer Olympic Games.
-
D.
previousSummerOlympics
Indicates that one Olympic Games event occurred immediately before another in the chronological sequence of Summer Olympic Games.
-
E.
sameYearSummerOlympics
Indicates that two events or entities are associated with Summer Olympic Games held in the same calendar year.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4982e0819087a9fcb2fa88541f |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.