Triple
T15706290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grosvenor House Hotel |
E380718
|
entity |
| Predicate | Great RoomKnownFor |
P6080
|
FINISHED |
| Object | large banqueting hall |
—
|
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: large banqueting hall | Statement: [Grosvenor House Hotel, Great RoomKnownFor, large banqueting hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Great RoomKnownFor Context triple: [Grosvenor House Hotel, Great RoomKnownFor, large banqueting hall]
-
A.
houseCommonRoom
Indicates that a house or dwelling includes or is associated with a shared common room space used collectively by its occupants.
-
B.
hallLocatedAt
Indicates that a hall is situated at or within a specific location or address.
-
C.
mainChamber
Indicates that something is the primary or central chamber or room within a larger structure or system.
-
D.
hall
Indicates that an entity is a hall, i.e., a large room or building space used for gatherings, events, or passage.
-
E.
hasMainHall
chosen
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.