Triple
T23615734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago house |
E583166
|
entity |
| Predicate | notableVenueAssociated |
P134947
|
FINISHED |
| Object | The Warehouse |
—
|
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: The Warehouse | Statement: [Chicago house, notableVenueAssociated, The Warehouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVenueAssociated Context triple: [Chicago house, notableVenueAssociated, The Warehouse]
-
A.
notableVenueFor
Indicates that a venue is especially recognized or significant for hosting, presenting, or being associated with a particular entity or activity.
-
B.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
C.
notableVenueRole
Indicates that an entity holds or has held a significant functional role or position at a particular venue or location.
-
D.
venueAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
-
E.
notableEventHostedAtReferredVenue
Indicates that a notable event was hosted at, or took place in, the referenced venue.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b174f6d881908416631229598fbb |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:45 p.m.