Triple
T28988131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pizzo di Claro |
E734746
|
entity |
| Predicate | hasMountainHutOnRoute |
P54950
|
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: [Pizzo di Claro, hasMountainHutOnRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountainHutOnRoute Context triple: [Pizzo di Claro, hasMountainHutOnRoute, yes]
-
A.
hasMountainHut
Indicates that one entity possesses, contains, or is associated with a mountain hut located within its area or domain.
-
B.
hasMountainHutsNearby
chosen
Indicates that a location or geographic feature has one or more mountain huts situated in its nearby surroundings.
-
C.
mountainHutOperator
Indicates that one entity operates, manages, or runs a particular mountain hut.
-
D.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
E.
hasPopularAscentRouteFrom
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 28, 2026, 9:15 a.m.