Triple
T37360513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 UEFA Europa League Final |
E927563
|
entity |
| Predicate | venueSelectionDate |
P187772
|
FINISHED |
| Object | 10 December 2010 |
—
|
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: 10 December 2010 | Statement: [2013 UEFA Europa League Final, venueSelectionDate, 10 December 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueSelectionDate Context triple: [2013 UEFA Europa League Final, venueSelectionDate, 10 December 2010]
-
A.
venueSelection
Indicates the relationship in which a specific venue is chosen or designated for an event, activity, or purpose among available options.
-
B.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
C.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
D.
feastBeginsOn
Indicates that the start time or date of a feast coincides with a specified time or date.
-
E.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.