Triple
T13381930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education City Stadium |
E319338
|
entity |
| Predicate | seatingCapacityDuring2022FIFAWorldCup |
P102103
|
FINISHED |
| Object | 40000 |
—
|
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: 40000 | Statement: [Education City Stadium, seatingCapacityDuring2022FIFAWorldCup, 40000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityDuring2022FIFAWorldCup Context triple: [Education City Stadium, seatingCapacityDuring2022FIFAWorldCup, 40000]
-
A.
capacityForWorldCup
chosen
Indicates the maximum number of spectators a venue can accommodate specifically for World Cup events.
-
B.
venueCapacityApproximate
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
C.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
D.
officialCapacities
Indicates that the relationship or action is performed in an entity’s formal, authorized, or institutional role rather than in a personal or informal capacity.
-
E.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce694788190881d1feac5b75720 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.