Triple
T12804401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of New York Clubs |
E306105
|
entity |
| Predicate | relatedToVenueType |
P10640
|
FINISHED |
| Object | nightclub |
—
|
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: nightclub | Statement: [King of New York Clubs, relatedToVenueType, nightclub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToVenueType Context triple: [King of New York Clubs, relatedToVenueType, nightclub]
-
A.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
-
C.
associatedWithVenueSecondaryUse
Indicates that an entity has a secondary or supplementary association with a particular venue, beyond its primary or main use.
-
D.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
E.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7e3be48190ba9159c9f1ac2ccd |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.