Triple
T14279038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 UEFA Champions League Final |
E353992
|
entity |
| Predicate | hostStadiumCapacityApprox |
P13599
|
FINISHED |
| Object | 80000 |
—
|
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: 80000 | Statement: [2016 UEFA Champions League Final, hostStadiumCapacityApprox, 80000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStadiumCapacityApprox Context triple: [2016 UEFA Champions League Final, hostStadiumCapacityApprox, 80000]
-
A.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
C.
hostStadium
Indicates that a particular stadium serves as the venue where an event, team, or competition is hosted.
-
D.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
E.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6585270c8190a717127b2f5dab3b |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.