Triple
T32272701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de Mulas route |
E824455
|
entity |
| Predicate | baseCampType |
P173911
|
FINISHED |
| Object | large high-altitude base camp with services |
—
|
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: large high-altitude base camp with services | Statement: [Plaza de Mulas route, baseCampType, large high-altitude base camp with services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseCampType Context triple: [Plaza de Mulas route, baseCampType, large high-altitude base camp with services]
-
A.
aboveBaseCamp
Indicates that one entity is located at a higher vertical position or elevation than the base camp.
-
B.
typicalBaseCampArea
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
-
C.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
D.
campLocation
Indicates the place or area where a camp is set up or located.
-
E.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc8d0ecc8190b33b0e37bd0d443e |
completed | May 3, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:42 a.m.