Triple
T8605965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carter Barron Amphitheatre |
E203795
|
entity |
| Predicate | isPublicVenue |
P6399
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Carter Barron Amphitheatre, isPublicVenue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicVenue Context triple: [Carter Barron Amphitheatre, isPublicVenue, true]
-
A.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
B.
homeVenueOpened
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
-
C.
isPublicBuilding
chosen
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
-
D.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
isPublicEvent
Indicates that an event is open and accessible to the general public rather than restricted to a private or limited audience.
- 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.