Triple
T1296786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tottenham Hotspur Stadium |
E27669
|
entity |
| Predicate | southStandCapacityApprox |
P13599
|
FINISHED |
| Object | 17000 |
—
|
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: 17000 | Statement: [Tottenham Hotspur Stadium, southStandCapacityApprox, 17000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southStandCapacityApprox Context triple: [Tottenham Hotspur Stadium, southStandCapacityApprox, 17000]
-
A.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
E.
numberOfStandingPlaces
Indicates the total count of standing-only positions or spots available in a given context (e.g., a vehicle, venue, or area).
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.