Triple
T11125480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at the Ryman |
E263123
|
entity |
| Predicate | recordingVenueType |
P24246
|
FINISHED |
| Object | historic concert hall |
—
|
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: historic concert hall | Statement: [Live at the Ryman, recordingVenueType, historic concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingVenueType Context triple: [Live at the Ryman, recordingVenueType, historic concert hall]
-
A.
recordSettingVenueFor
Indicates the venue or location where a particular record (such as a performance, achievement, or measurement) was set.
-
B.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
C.
notableRecordingVenueFor
chosen
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
D.
recordStoreVenue
Indicates a venue that functions as or is associated with a record store.
-
E.
auditoriumType
Indicates the specific kind or category of auditorium associated with an entity.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82fc5f88190b34c55de3d50f6a7 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.