Triple
T4252596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exposition Park |
E95890
|
entity |
| Predicate | plannedToHost |
P54963
|
FINISHED |
| Object | 2028 Summer Olympics events |
—
|
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: 2028 Summer Olympics events | Statement: [Exposition Park, plannedToHost, 2028 Summer Olympics events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedToHost Context triple: [Exposition Park, plannedToHost, 2028 Summer Olympics events]
-
A.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
B.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
C.
roleOfHost
Indicates that an entity serves as the host in relation to another entity, event, or interaction.
-
D.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
E.
alsoHosted
Indicates that the subject entity, in addition to others, served as a host for the same event or activity.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebc98e08190915ac309a51ef87f |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.