Triple
T35122627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 2001–02 |
E1014201
|
entity |
| Predicate | finalStadiumUsedDueTo |
P115926
|
FINISHED |
| Object | Wembley Stadium redevelopment |
—
|
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: Wembley Stadium redevelopment | Statement: [FA Cup 2001–02, finalStadiumUsedDueTo, Wembley Stadium redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalStadiumUsedDueTo Context triple: [FA Cup 2001–02, finalStadiumUsedDueTo, Wembley Stadium redevelopment]
-
A.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
-
C.
venueOfFinalMatch
chosen
Indicates the location where the final match of a competition or tournament is held.
-
D.
usedAsOlympicStadiumFor
Indicates that a venue served as the official stadium for hosting events of a particular edition of the Olympic Games.
-
E.
finalSeasonAtVenue
Indicates that a particular season is the last one in which an entity (such as a team or event) takes place at a given 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:01 p.m.