Triple
T2826315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champion Stadium |
E54930
|
entity |
| Predicate | hasInfieldSeating |
P40699
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Champion Stadium, hasInfieldSeating, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfieldSeating Context triple: [Champion Stadium, hasInfieldSeating, yes]
-
A.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
B.
hasClubSeats
Indicates that an entity (such as a venue or section) includes or is equipped with club-level seating.
-
C.
hasSeatingSections
Indicates that an entity is divided into distinct seating areas or sections designated for occupants.
-
D.
hasGrassSeatingArea
chosen
Indicates that an entity includes or provides a seating area located on a grass surface.
-
E.
hasGeneralSeats
Indicates that an entity possesses or includes general (non-reserved) seats in a seating or allocation context.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde94ba848190b2c990936e07e6bb |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.