Triple
T1746410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagano Olympic Stadium |
E38344
|
entity |
| Predicate | olympicFunction |
P21212
|
FINISHED |
| Object | ceremonies venue |
—
|
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: ceremonies venue | Statement: [Nagano Olympic Stadium, olympicFunction, ceremonies venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olympicFunction Context triple: [Nagano Olympic Stadium, olympicFunction, ceremonies venue]
-
A.
hasOlympicFunction
chosen
Indicates that an entity serves a specific role, duty, or function within the context of the Olympic Games or Olympic movement.
-
B.
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).
-
C.
OlympicGoldMedalSport
Indicates that the subject sport is one in which the object athlete or team has won an Olympic gold medal.
-
D.
olympicCommittee
Indicates that an entity serves as, belongs to, or is officially associated with an Olympic committee in relation to another entity.
-
E.
OlympicGamesParticipated
Indicates that an entity has taken part as a competitor in one or more editions of 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab630e7d008190a8c673665d9672bb |
completed | March 6, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69aa61c5a18481909bc49e0c54d64314 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.