Triple
T13805831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada at the Youth Olympic Games |
E331757
|
entity |
| Predicate | summerGamesFrequency |
P110940
|
FINISHED |
| Object | every four years |
—
|
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: every four years | Statement: [Canada at the Youth Olympic Games, summerGamesFrequency, every four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerGamesFrequency Context triple: [Canada at the Youth Olympic Games, summerGamesFrequency, every four years]
-
A.
OlympicFrequency
chosen
Indicates how often a particular Olympic event, competition, or occurrence takes place within the Olympic cycle.
-
B.
gamesFrequency
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
C.
olympicGames
Indicates that an entity is an edition or instance of the Olympic Games event.
-
D.
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.
-
E.
olympicGamesNumber
Indicates the specific edition number assigned to a particular occurrence of the Olympic Games.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026d98108190acf366a36d97bf92 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.