Triple
T15291864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Summer Olympics athletics stadium |
E365546
|
entity |
| Predicate | postOlympicConversion |
P117981
|
FINISHED |
| Object | baseball stadium |
—
|
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: baseball stadium | Statement: [1996 Summer Olympics athletics stadium, postOlympicConversion, baseball stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOlympicConversion Context triple: [1996 Summer Olympics athletics stadium, postOlympicConversion, baseball stadium]
-
A.
postOlympicName
Indicates that one entity is the new name given to another entity after the Olympic Games.
-
B.
postOlympicTenant
Indicates that an entity serves as a tenant or occupant of a facility or venue after the conclusion of the Olympic Games.
-
C.
postOlympicsCapacity
Indicates the seating or usage capacity of a venue after the Olympic Games have concluded.
-
D.
openedForOlympics
Indicates that something was opened or inaugurated specifically in preparation for or in conjunction with the Olympic Games.
-
E.
olympicGoldWith
Indicates that the related entities won an Olympic gold medal together, typically as teammates in the same event or competition.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03680b60c8190a3ea54a9d34c8105 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:15 a.m.