Triple
T22224536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Letter |
E549300
|
entity |
| Predicate | associatedPerformanceVenueType |
P134947
|
FINISHED |
| Object | Las Vegas showroom |
—
|
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: Las Vegas showroom | Statement: [The Letter, associatedPerformanceVenueType, Las Vegas showroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPerformanceVenueType Context triple: [The Letter, associatedPerformanceVenueType, Las Vegas showroom]
-
A.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
B.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
C.
laterPerformanceVenue
Indicates that a performance or event took place at this venue at a later time than another referenced performance or venue.
-
D.
recordedAtVenueType
Indicates that an event or recording took place at a venue of a specified type (e.g., studio, concert hall, stadium).
-
E.
venueAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b93e2208190aee70ffd82962ea0 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.