Triple
T37360514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 UEFA Europa League Final |
E927563
|
entity |
| Predicate | venueSelectionBody |
P18587
|
FINISHED |
| Object | UEFA Executive Committee |
—
|
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: UEFA Executive Committee | Statement: [2013 UEFA Europa League Final, venueSelectionBody, UEFA Executive Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueSelectionBody Context triple: [2013 UEFA Europa League Final, venueSelectionBody, UEFA Executive Committee]
-
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.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
C.
venueSelectionDate
Indicates the date on which a venue is chosen or confirmed for an event or activity.
-
D.
venuePattern
Indicates a recurring or characteristic arrangement, schedule, or configuration associated with a particular venue.
-
E.
venueConcept
Indicates a relationship where a venue is associated with, characterized by, or defined in terms of a particular concept or thematic idea.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.