Triple
T8023776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 2005–06 |
E186801
|
entity |
| Predicate | finalHostStadiumCapacityApprox |
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: [UEFA Champions League 2005–06, finalHostStadiumCapacityApprox, 80000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalHostStadiumCapacityApprox Context triple: [UEFA Champions League 2005–06, finalHostStadiumCapacityApprox, 80000]
-
A.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
B.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
C.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
D.
formerStadiumCapacityApprox
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
-
E.
hostStadium
Indicates that a particular stadium serves as the venue where an event, team, or competition is hosted.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e90c7348190abc1013a312e4f1a |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.