Triple
T38057093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Stadionclub |
E950233
|
entity |
| Predicate | associatedStadiumCapacityRange |
—
|
GENERATED |
| Object | over 40,000 spectators |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStadiumCapacityRange Context triple: [De Stadionclub, associatedStadiumCapacityRange, over 40,000 spectators]
-
A.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
B.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
C.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
E.
hasBallparkCapacityCategory
Indicates the classification of a ballpark’s seating capacity into a predefined size or capacity category.
- F. None of above.
Provenance (1 batch)
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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.