Triple
T30678469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ehrwalder Sonnenspitze |
E780982
|
entity |
| Predicate | hasAlpineHutNearby |
P54950
|
FINISHED |
| Object | Ehrwalder Alm |
—
|
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: Ehrwalder Alm | Statement: [Ehrwalder Sonnenspitze, hasAlpineHutNearby, Ehrwalder Alm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlpineHutNearby Context triple: [Ehrwalder Sonnenspitze, hasAlpineHutNearby, Ehrwalder Alm]
-
A.
hasMountainHutsNearby
chosen
Indicates that a location or geographic feature has one or more mountain huts situated in its nearby surroundings.
-
B.
hasMountainHut
Indicates that one entity possesses, contains, or is associated with a mountain hut located within its area or domain.
-
C.
hasSkiResortNearby
Indicates that one location is situated close enough to another location that it can be considered to have a ski resort in its vicinity.
-
D.
isAlpineResort
Indicates that the subject is a resort located in, or characteristic of, an alpine (mountainous) region.
-
E.
hasBackcountryLodge
Indicates that one entity possesses, contains, or is associated with a backcountry lodge located in a remote or wilderness area.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 8:32 p.m.