Triple
T17038094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mixed short track speed skating relay |
E413372
|
entity |
| Predicate | isOlympic |
P15215
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [mixed short track speed skating relay, isOlympic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOlympic Context triple: [mixed short track speed skating relay, isOlympic, true]
-
A.
OlympicStatus
chosen
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
-
B.
hasOlympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Olympic Games or Olympic movement.
-
C.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
D.
hasOlympians
Indicates that an entity includes, is associated with, or contains one or more Olympian participants or members.
-
E.
openedForOlympics
Indicates that something was opened or inaugurated specifically in preparation for or in conjunction with 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f45f84819092cfb27cc33da026 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.