Triple
T273915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2028 Summer Olympics |
E5204
|
entity |
| Predicate | venueConcept |
P8643
|
FINISHED |
| Object | use of existing and temporary venues |
—
|
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: use of existing and temporary venues | Statement: [2028 Summer Olympics, venueConcept, use of existing and temporary venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueConcept Context triple: [2028 Summer Olympics, venueConcept, use of existing and temporary venues]
-
A.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
B.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
C.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
D.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd0a99c819089968a5400c58c5f |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.