Triple
T13177466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Hotel, Bradford |
E313134
|
entity |
| Predicate | hasBanquetingSuites |
P74384
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Midland Hotel, Bradford, hasBanquetingSuites, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBanquetingSuites Context triple: [Midland Hotel, Bradford, hasBanquetingSuites, yes]
-
A.
hasLuxurySuites
Indicates that an entity provides or contains high-end, premium-quality suites as part of its accommodations or offerings.
-
B.
hasConventionHalls
Indicates that an entity possesses or includes one or more convention halls as part of its facilities or infrastructure.
-
C.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
-
D.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
-
E.
hasBallrooms
chosen
Indicates that an entity possesses or contains one or more ballrooms as part of its facilities or structure.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.