Triple
T25285414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammons Field |
E633922
|
entity |
| Predicate | hasReservedSeating |
P9399
|
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: [Hammons Field, hasReservedSeating, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservedSeating Context triple: [Hammons Field, hasReservedSeating, yes]
-
A.
hasReservedSeats
chosen
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
B.
hasPrioritySeating
Indicates that one entity provides or designates reserved or preferential seating for another entity.
-
C.
hasSeatStatus
Indicates the current condition or availability state of a seat in a given context.
-
D.
hasPlannedSeatingType
Indicates that a specific type or arrangement of seating has been planned or designated for an event, venue, or context.
-
E.
hasSeatingClassification
Indicates that an entity is assigned a specific type or category of seating arrangement or capacity.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 21, 2026, 1:19 p.m.