Triple
T19657325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West 52nd Street |
E471981
|
entity |
| Predicate | hasFormerVenueType |
P136847
|
FINISHED |
| Object | jazz club |
—
|
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: jazz club | Statement: [West 52nd Street, hasFormerVenueType, jazz club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerVenueType Context triple: [West 52nd Street, hasFormerVenueType, jazz club]
-
A.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
B.
hasFormerStation
Indicates that an entity previously had a particular station (e.g., a stop, depot, or facility) that is no longer in active use or part of its current infrastructure.
-
C.
venueFormerName
Indicates that a venue previously had a different official name than it has currently.
-
D.
hasFormerAirport
Indicates that an entity previously had an airport that is no longer in operation or no longer exists.
-
E.
formerHomeVenue
Indicates that a location previously served as the primary venue or home ground for an entity, but no longer holds that status.
- F. None of above. chosen
Provenance (4 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641475f408190bd42ef3f8d590719 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.