Triple
T20419510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satchmo at Symphony Hall |
E500808
|
entity |
| Predicate | recordedInVenueType |
P117072
|
FINISHED |
| Object | 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: concert hall | Statement: [Satchmo at Symphony Hall, recordedInVenueType, concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedInVenueType Context triple: [Satchmo at Symphony Hall, recordedInVenueType, concert hall]
-
A.
recordedAtVenueType
chosen
Indicates that an event or recording took place at a venue of a specified type (e.g., studio, concert hall, stadium).
-
B.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
C.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
D.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
E.
recordSettingVenueFor
Indicates the venue or location where a particular record (such as a performance, achievement, or measurement) was set.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba39f7081909358f1103a0f241c |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.