Triple
T2512943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chukchansi Park |
E52741
|
entity |
| Predicate | hasOutfieldSeating |
P16726
|
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: [Chukchansi Park, hasOutfieldSeating, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldSeating Context triple: [Chukchansi Park, hasOutfieldSeating, yes]
-
A.
hasOutfieldFeature
chosen
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
B.
hasClubSeats
Indicates that an entity (such as a venue or section) includes or is equipped with club-level seating.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
hasSeatingSections
Indicates that an entity is divided into distinct seating areas or sections designated for occupants.
-
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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.