Triple
T31850160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinnin' Deep |
E813043
|
entity |
| Predicate | typicalVenueUse |
P25526
|
FINISHED |
| Object | clubs |
—
|
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: clubs | Statement: [Spinnin' Deep, typicalVenueUse, clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVenueUse Context triple: [Spinnin' Deep, typicalVenueUse, clubs]
-
A.
typicalVenueSetting
Indicates the usual or characteristic type of venue or setting in which an event, activity, or interaction typically takes place.
-
B.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
C.
formerTypicalVenue
Indicates that a location was once the usual or primary venue for an entity’s activities or events, but no longer serves in that typical role.
-
D.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
-
E.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:51 p.m.