Triple
T12543003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Los Angeles theater community |
E299888
|
entity |
| Predicate | includesTypeOfVenue |
P10640
|
FINISHED |
| Object | regional theaters |
—
|
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: regional theaters | Statement: [Greater Los Angeles theater community, includesTypeOfVenue, regional theaters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTypeOfVenue Context triple: [Greater Los Angeles theater community, includesTypeOfVenue, regional theaters]
-
A.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
C.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
-
D.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
E.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.