Triple
T26405039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Pelmo |
E663808
|
entity |
| Predicate | hasHutNearby |
P54950
|
FINISHED |
| Object | Rifugio Venezia al Pelmo |
—
|
NE NERFINISHED |
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: Rifugio Venezia al Pelmo | Statement: [Monte Pelmo, hasHutNearby, Rifugio Venezia al Pelmo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHutNearby Context triple: [Monte Pelmo, hasHutNearby, Rifugio Venezia al Pelmo]
-
A.
hasAssociatedHut
Indicates that one entity is linked or connected to a specific hut as its associated structure.
-
B.
hasMountainHutsNearby
chosen
Indicates that a location or geographic feature has one or more mountain huts situated in its nearby surroundings.
-
C.
hasMountainHut
Indicates that one entity possesses, contains, or is associated with a mountain hut located within its area or domain.
-
D.
hasNearbyLodge
Indicates that one entity is located close to or in the vicinity of a lodge associated with another entity.
-
E.
nearestHut
Indicates that one hut is the closest in distance to a given reference point or entity compared to all other huts.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 11:34 p.m.