Triple
T6643611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League Final 2024 |
E150644
|
entity |
| Predicate | venueHostSelectionDate |
P18587
|
FINISHED |
| Object | 24 May 2022 |
—
|
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: 24 May 2022 | Statement: [UEFA Champions League Final 2024, venueHostSelectionDate, 24 May 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueHostSelectionDate Context triple: [UEFA Champions League Final 2024, venueHostSelectionDate, 24 May 2022]
-
A.
venueSelection
chosen
Indicates the relationship in which a specific venue is chosen or designated for an event, activity, or purpose among available options.
-
B.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
E.
organizerOfFinalVenueSelection
Indicates the entity that is responsible for organizing or managing the process of selecting the final venue.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.