Triple
T33674926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maratea |
E862731
|
entity |
| Predicate | hasPanoramicRoad |
P17006
|
FINISHED |
| Object | coastal road with sea views |
—
|
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: coastal road with sea views | Statement: [Maratea, hasPanoramicRoad, coastal road with sea views]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanoramicRoad Context triple: [Maratea, hasPanoramicRoad, coastal road with sea views]
-
A.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
hasPanoramaArea
Indicates that something includes or is associated with a designated area intended for panoramic viewing or wide-angle observation.
-
C.
hasScenicRoutes
Indicates that one location, path, or area offers routes that are visually attractive or notable for their natural or aesthetic scenery.
-
D.
hasSummitPanorama
Indicates that a summit location offers a panoramic view or image captured from its highest point.
-
E.
hasScenicDrive
chosen
Indicates that one entity offers or features a visually appealing or picturesque driving route associated with it.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 1, 2026, 1:43 a.m.