Triple
T30807265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Ballet |
E784537
|
entity |
| Predicate | performanceVenueLocation |
P140443
|
FINISHED |
| Object | Dallas, Texas |
—
|
NE NERFINISHED |
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: Dallas, Texas | Statement: [Dallas Ballet, performanceVenueLocation, Dallas, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceVenueLocation Context triple: [Dallas Ballet, performanceVenueLocation, Dallas, Texas]
-
A.
coVenueWith
Indicates that two events or activities take place at the same venue or location.
-
B.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
C.
formerVenueLocation
Indicates that a location previously served as the venue for an entity or event but no longer does so.
-
D.
eventLocationDetail
chosen
Indicates the specific place or venue where an event occurs, often providing more granular location information than a general address or area.
-
E.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 8:43 p.m.