Triple
T3364064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dorchester Hotel |
E70791
|
entity |
| Predicate | hasConferenceFacility |
P15338
|
FINISHED |
| Object | banqueting halls |
—
|
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: banqueting halls | Statement: [The Dorchester Hotel, hasConferenceFacility, banqueting halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceFacility Context triple: [The Dorchester Hotel, hasConferenceFacility, banqueting halls]
-
A.
hasConferenceSpace
chosen
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
-
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
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
D.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
E.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb28467b88190bdf70b851bc8efa9 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.