Triple
T26182298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadelgrat |
E654717
|
entity |
| Predicate | hasSummitOnRidge |
P167487
|
FINISHED |
| Object | Nadelhorn |
—
|
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: Nadelhorn | Statement: [Nadelgrat, hasSummitOnRidge, Nadelhorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitOnRidge Context triple: [Nadelgrat, hasSummitOnRidge, Nadelhorn]
-
A.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
B.
hasSummitRidgeOrientation
Indicates the directional alignment or orientation of a summit ridge relative to cardinal or geographic directions.
-
C.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
D.
hasSummitAbove
Indicates that one summit is located at a higher elevation than another summit.
-
E.
isOnRidgeWith
chosen
Indicates that two or more entities are located together along the same ridge or elevated crest.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 8:40 p.m.