Triple
T2280060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinness Storehouse |
E51259
|
entity |
| Predicate | observationDeckView |
P9193
|
FINISHED |
| Object | panoramic view of Dublin |
—
|
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: panoramic view of Dublin | Statement: [Guinness Storehouse, observationDeckView, panoramic view of Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationDeckView Context triple: [Guinness Storehouse, observationDeckView, panoramic view of Dublin]
-
A.
observationDeckFloor
Indicates the specific floor or level of a building on which an observation deck is located.
-
B.
observationDeckHeight
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
C.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
D.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
E.
hasScenicViewOf
chosen
Indicates that one entity offers a visually appealing or picturesque view of another entity.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21ac3d48190abef254e1c3f45e8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.