Triple
T9678779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Casbah Coffee Club |
E234229
|
entity |
| Predicate | performanceArea |
P89589
|
FINISHED |
| Object | cellar |
—
|
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: cellar | Statement: [The Casbah Coffee Club, performanceArea, cellar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceArea Context triple: [The Casbah Coffee Club, performanceArea, cellar]
-
A.
performanceRegion
Indicates the geographic or market area within which a performance, operation, or activity takes place or is evaluated.
-
B.
performanceClass
Indicates the category or level of performance to which an entity is assigned, typically reflecting its capabilities or quality tier.
-
C.
performanceFocus
Indicates that an entity directs attention or effort toward improving or emphasizing performance in a given context.
-
D.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
E.
performanceStructure
Indicates the structural or organizational arrangement that underlies how a performance or event is composed, ordered, or presented.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9b01708190aaf51cf4d36015a0 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:16 p.m.