Triple
T8343781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapurna Conservation Area |
E195983
|
entity |
| Predicate | ThorongLaElevation |
P82203
|
FINISHED |
| Object | 5416 metres |
—
|
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: 5416 metres | Statement: [Annapurna Conservation Area, ThorongLaElevation, 5416 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ThorongLaElevation Context triple: [Annapurna Conservation Area, ThorongLaElevation, 5416 metres]
-
A.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
B.
elevationRangeUpperBound
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
-
C.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
D.
thirdHighestPeak
Indicates that the subject is the third tallest peak (by elevation or prominence) within a specified set, region, or ranking.
-
E.
pilgrimageAltitudeHighPoint
Indicates the highest altitude reached along a pilgrimage route or during a pilgrimage journey.
- F. None of above. chosen
Provenance (4 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7febde288190bf4677fb24d26b83 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:58 p.m.