Triple
T35888773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Generoso |
E1037724
|
entity |
| Predicate | hasPanoramicRestaurant |
P52138
|
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: [Monte Generoso, hasPanoramicRestaurant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanoramicRestaurant Context triple: [Monte Generoso, hasPanoramicRestaurant, yes]
-
A.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
hasDiningComponent
Indicates that something includes or is associated with a dining-related part, feature, or function.
-
C.
hasPanoramaArea
Indicates that something includes or is associated with a designated area intended for panoramic viewing or wide-angle observation.
-
D.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
E.
hasRevolvingRestaurant
chosen
Indicates that one entity features or contains a restaurant that rotates around a central axis, typically providing a 360-degree view.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 3, 2026, 4:06 p.m.