Triple
T16187033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IG Field |
E392832
|
entity |
| Predicate | countrySportContext |
P98278
|
FINISHED |
| Object | Canadian football in Canada |
—
|
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: Canadian football in Canada | Statement: [IG Field, countrySportContext, Canadian football in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countrySportContext Context triple: [IG Field, countrySportContext, Canadian football in Canada]
-
A.
countrySportAssociation
chosen
Indicates a relationship where a country is associated with, participates in, or is represented in a particular sport or sporting activity.
-
B.
nationalSportContext
Indicates that a particular sport is recognized or designated as the national sport of a given country or region within a specific contextual framework.
-
C.
stateSport
Indicates that a particular sport is officially associated with, designated by, or representative of a given state.
-
D.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
E.
sportsRegionOf
Indicates that a region is the geographic or administrative area associated with a particular sports entity or activity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e220630db481908a0c7f7170f20c5f |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.