Triple
T7918333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manaslu Circuit Trek |
E183881
|
entity |
| Predicate | nearbyPeakElevation |
P73906
|
FINISHED |
| Object | 8163 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: 8163 m | Statement: [Manaslu Circuit Trek, nearbyPeakElevation, 8163 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPeakElevation Context triple: [Manaslu Circuit Trek, nearbyPeakElevation, 8163 m]
-
A.
nearbyElevation
chosen
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
B.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
C.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
D.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
E.
areaPeakApprox
Indicates an approximate measurement or estimation of the peak area associated with an entity or event.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.