Triple
T262200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China |
E5561
|
entity |
| Predicate | olympicHost |
P5968
|
FINISHED |
| Object | hosted 2008 Summer Olympics in Beijing |
—
|
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: hosted 2008 Summer Olympics in Beijing | Statement: [China, olympicHost, hosted 2008 Summer Olympics in Beijing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olympicHost Context triple: [China, olympicHost, hosted 2008 Summer Olympics in Beijing]
-
A.
olympicHostCountry
chosen
Indicates that a country served as the official host nation for a particular edition of the Olympic Games.
-
B.
olympicHostState
Indicates that a state served as the official host location for a particular edition of the Olympic Games.
-
C.
olympicOpeningDate
Indicates the calendar date on which a specific edition of the Olympic Games officially begins with its opening ceremony.
-
D.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
-
E.
olympicCommittee
Indicates that an entity serves as, belongs to, or is officially associated with an Olympic committee in relation to another entity.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.