Triple
T9146613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Power Stadium |
E219472
|
entity |
| Predicate | capacityForFootball |
P13599
|
FINISHED |
| Object | 32312 |
—
|
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: 32312 | Statement: [King Power Stadium, capacityForFootball, 32312]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityForFootball Context triple: [King Power Stadium, capacityForFootball, 32312]
-
A.
capacityForBasketball
Indicates the ability or suitability of an entity to play or perform well in basketball.
-
B.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
C.
infieldCapacity
Indicates the maximum number of entities that can be accommodated within a defined infield area or region.
-
D.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
E.
capacityBaseball
Indicates the maximum number of spectators that a baseball venue is designed or allowed to hold.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca917914c8190b97ca9169bbd1e5e |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.