Triple
T30506917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 2007–08 |
E776299
|
entity |
| Predicate | finalStadiumCapacityApprox |
P27055
|
FINISHED |
| Object | 48000 |
—
|
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: 48000 | Statement: [UEFA Cup 2007–08, finalStadiumCapacityApprox, 48000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalStadiumCapacityApprox Context triple: [UEFA Cup 2007–08, finalStadiumCapacityApprox, 48000]
-
A.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
B.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
C.
stadiumCapacityContext
chosen
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
D.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
E.
formerStadiumCapacityApprox
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:15 p.m.