Triple
T3713726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammersmith |
E81474
|
entity |
| Predicate | hasEntertainmentFunction |
P23473
|
FINISHED |
| Object | live music venue |
—
|
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: live music venue | Statement: [Hammersmith, hasEntertainmentFunction, live music venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntertainmentFunction Context triple: [Hammersmith, hasEntertainmentFunction, live music venue]
-
A.
hasQueueEntertainment
Indicates that an entity provides or features entertainment specifically for people waiting in a queue.
-
B.
hasEntertainmentVenue
chosen
Indicates that an entity possesses, contains, or is associated with an entertainment venue as part of its facilities or offerings.
-
C.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
D.
hasCulturalFunction
Indicates that something serves a particular role, purpose, or function within a culture or cultural context.
-
E.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9ccfad081908730ed15c6f87ce2 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.