Triple
T37671075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus and Latvia |
E937957
|
entity |
| Predicate | tournamentDiscipline |
P179726
|
FINISHED |
| Object | men's ice 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: men's ice hockey | Statement: [Belarus and Latvia, tournamentDiscipline, men's ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentDiscipline Context triple: [Belarus and Latvia, tournamentDiscipline, men's ice hockey]
-
A.
inSportDiscipline
chosen
Indicates that an entity participates, competes, or is involved in a specific sport discipline or event.
-
B.
sportDisciplineScope
Indicates the specific sport discipline or category within which a given relationship, rule, or activity is defined or applies.
-
C.
WorldCupDiscipline
Indicates a disciplinary action (such as a card, suspension, or sanction) imposed on an entity in the context of a FIFA World Cup competition.
-
D.
worldCupDiscipline
Indicates a disciplinary action (such as a card, suspension, or sanction) given to an entity in the context of a World Cup competition.
-
E.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e5be808190aa4e01219b36df80 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.