Triple
T8605980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carter Barron Amphitheatre |
E203795
|
entity |
| Predicate | hasOutdoorStatus |
P8618
|
FINISHED |
| Object | open-air venue |
—
|
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: open-air venue | Statement: [Carter Barron Amphitheatre, hasOutdoorStatus, open-air venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorStatus Context triple: [Carter Barron Amphitheatre, hasOutdoorStatus, open-air venue]
-
A.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
B.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
C.
isOutdoor
chosen
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
D.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
E.
hasOutdoorStage
Indicates that an entity includes or is equipped with a stage located outdoors for performances or events.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46e9b6a881908f6a6c847519e5e5 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.