Triple
T6311735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyeongchang Olympic Stadium |
E141518
|
entity |
| Predicate | postGamesPlan |
P69989
|
FINISHED |
| Object | demolition and site redevelopment |
—
|
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: demolition and site redevelopment | Statement: [Pyeongchang Olympic Stadium, postGamesPlan, demolition and site redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postGamesPlan Context triple: [Pyeongchang Olympic Stadium, postGamesPlan, demolition and site redevelopment]
-
A.
postGamesUse
Indicates that an entity uses or engages with something after games have concluded.
-
B.
previousGames
Indicates that one entity represents games that occurred earlier in time relative to another entity.
-
C.
homeRankingPreGame
Indicates the pre-game ranking or standing assigned to the home team before the event begins.
-
D.
homeGamesOf
Indicates that the subject is a home game (or set of home games) played by the specified team or entity.
-
E.
primaryGameDay
Indicates the main or most significant day on which a game or sporting event is scheduled or typically played.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649d1e048190a3fc7fbce9d2ee57 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.