Triple
T13367994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Balcon Nord trail |
E318989
|
entity |
| Predicate | hasApproximateElevationMax |
P19320
|
FINISHED |
| Object | ~2100 m |
—
|
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: ~2100 m | Statement: [Grand Balcon Nord trail, hasApproximateElevationMax, ~2100 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateElevationMax Context triple: [Grand Balcon Nord trail, hasApproximateElevationMax, ~2100 m]
-
A.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
B.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
C.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.