Triple
T5603099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League Final 2011 |
E147166
|
entity |
| Predicate | venueRebuilt |
P65009
|
FINISHED |
| Object | new Wembley Stadium opened in 2007 |
—
|
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: new Wembley Stadium opened in 2007 | Statement: [UEFA Champions League Final 2011, venueRebuilt, new Wembley Stadium opened in 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueRebuilt Context triple: [UEFA Champions League Final 2011, venueRebuilt, new Wembley Stadium opened in 2007]
-
A.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
B.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
C.
venueManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a particular venue.
-
D.
reopenedAsConcertHall
Indicates that a previously closed or differently purposed venue has been opened again specifically to function as a concert hall.
-
E.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dce10c8190bf456602eec211d4 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:39 p.m.