Triple
T20630844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera Holland Park |
E506947
|
entity |
| Predicate | hasAudienceFacilities |
P12416
|
FINISHED |
| Object | bar |
—
|
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: bar | Statement: [Opera Holland Park, hasAudienceFacilities, bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceFacilities Context triple: [Opera Holland Park, hasAudienceFacilities, bar]
-
A.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
-
B.
hasMediaFacilities
Indicates that an entity possesses or provides access to media-related infrastructure or equipment (such as studios, recording, broadcasting, or production facilities).
-
C.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
D.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
E.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0b0508819093c62a4ceaf860ce |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.