Triple
T8601743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1000 m speed skating at the 1998 Winter Olympics |
E203691
|
entity |
| Predicate | isOlympicEvent |
P7488
|
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: [1000 m speed skating at the 1998 Winter Olympics, isOlympicEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOlympicEvent Context triple: [1000 m speed skating at the 1998 Winter Olympics, isOlympicEvent, true]
-
A.
OlympicStatus
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.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
C.
olympicGoldMedalInEvent
Indicates that an entity has won an Olympic gold medal in a specified sporting event.
-
D.
OlympicMedalEvent
chosen
Indicates that an entity represents a specific Olympic Games event in which medals are awarded.
-
E.
hasOlympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Olympic Games or Olympic movement.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46da609881909a6d851915e8df14 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.