Triple
T14928091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ameris Bank Amphitheatre |
E372183
|
entity |
| Predicate | hasLawnSeatingCapacity |
P22556
|
FINISHED |
| Object | approximately 7000 |
—
|
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: approximately 7000 | Statement: [Ameris Bank Amphitheatre, hasLawnSeatingCapacity, approximately 7000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLawnSeatingCapacity Context triple: [Ameris Bank Amphitheatre, hasLawnSeatingCapacity, approximately 7000]
-
A.
hasGrassSeatingArea
Indicates that an entity includes or provides a seating area located on a grass surface.
-
B.
outdoorSeating
Indicates that an establishment provides seating arrangements located outside the main indoor area.
-
C.
lawnCapacity
chosen
Indicates the maximum number of entities that can be accommodated or present on a given lawn at one time.
-
D.
hasShelteredSeating
Indicates that an entity provides seating that is protected from weather or other external elements.
-
E.
hasAdditionalBenchesAt
Indicates that one location or facility includes extra benches situated at or associated with another specified place.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:35 a.m.