Triple
T26837834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luge at the 2014 Winter Olympics |
E675685
|
entity |
| Predicate | firstTimeEvent |
P197762
|
FINISHED |
| Object | team relay |
—
|
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: team relay | Statement: [Luge at the 2014 Winter Olympics, firstTimeEvent, team relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTimeEvent Context triple: [Luge at the 2014 Winter Olympics, firstTimeEvent, team relay]
-
A.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
-
B.
firstTimeSince
Indicates that an event or state is occurring now after not having occurred since a specified prior time or reference event.
-
C.
firstTimeParticipation
Indicates that an entity is taking part in a specified event, activity, or context for the very first time.
-
D.
firstCreationAssociatedEvent
Indicates the event that is most closely associated with the initial creation of an entity.
-
E.
firstReleaseEvent
Indicates the event at which something (typically a creative work or product) was first officially released.
- F. None of above. chosen
Provenance (4 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69feaa477f7c81909382b3aa77e7e11c |
completed | May 9, 2026, 3:30 a.m. |
Created at: April 27, 2026, 5:05 a.m.