Triple
T14223602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 3 (Beijing Capital International Airport) |
E352559
|
entity |
| Predicate | openedFor2008Olympics |
P47611
|
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: [Terminal 3 (Beijing Capital International Airport), openedFor2008Olympics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedFor2008Olympics Context triple: [Terminal 3 (Beijing Capital International Airport), openedFor2008Olympics, true]
-
A.
openedForOlympics
chosen
Indicates that something was opened or inaugurated specifically in preparation for or in conjunction with the Olympic Games.
-
B.
olympicOpeningDate
Indicates the calendar date on which a specific edition of the Olympic Games officially begins with its opening ceremony.
-
C.
OlympicCity
Indicates that a city has been designated as a host location for the Olympic Games.
-
D.
OlympicVenue
Indicates that a location serves or has served as a site where official Olympic Games events are held.
-
E.
usedAsOlympicStadiumFor
Indicates that a venue served as the official stadium for hosting events of a particular edition 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6227c288819081473ce44f9f0934 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.