Triple
T29906793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Olympic Park |
E759559
|
entity |
| Predicate | mainVenueClusterFor |
P65326
|
FINISHED |
| Object | 2016 Summer Olympics |
—
|
NE NERFINISHED |
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: 2016 Summer Olympics | Statement: [Rio Olympic Park, mainVenueClusterFor, 2016 Summer Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVenueClusterFor Context triple: [Rio Olympic Park, mainVenueClusterFor, 2016 Summer Olympics]
-
A.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
B.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
-
C.
mainVenueCourse
Indicates that a particular course is primarily hosted or conducted at a specified main venue.
-
D.
hasPrincipalVenue
chosen
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67756337881908627f7068dc02d9f |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:08 p.m.