Triple
T22121365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Face-off |
E546676
|
entity |
| Predicate | mainSportContext |
P46432
|
FINISHED |
| Object | junior hockey |
—
|
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: junior hockey | Statement: [Face-off, mainSportContext, junior hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSportContext Context triple: [Face-off, mainSportContext, junior hockey]
-
A.
hasSportingContext
chosen
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
-
B.
mainSportExample
Indicates that the referenced sport is the primary or most representative sport associated with the given entity (such as a person, organization, or place).
-
C.
primarySportContent
Indicates that the subject is the main or central piece of sports-related content associated with the object.
-
D.
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.
-
E.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1297e7e188190873924403421caa2 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.