Triple
T37929437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern League ballparks |
E946172
|
entity |
| Predicate | typicalSeatingType |
P204481
|
FINISHED |
| Object | outdoor seating |
—
|
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: outdoor seating | Statement: [Eastern League ballparks, typicalSeatingType, outdoor seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeatingType Context triple: [Eastern League ballparks, typicalSeatingType, outdoor seating]
-
A.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
B.
typicalSeatCount
Indicates the usual or standard number of seats associated with an entity.
-
C.
hasFlexibleSeating
Indicates that an entity provides seating arrangements that can be easily rearranged, adjusted, or reconfigured to suit different uses or preferences.
-
D.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
E.
seatingDirection
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
- F. None of above. chosen
Provenance (4 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.