Triple
T3020448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inylchek Glacier |
E82440
|
entity |
| Predicate | hasCamp |
P7502
|
FINISHED |
| Object | base camp for Khan Tengri ascents |
—
|
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: base camp for Khan Tengri ascents | Statement: [Inylchek Glacier, hasCamp, base camp for Khan Tengri ascents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCamp Context triple: [Inylchek Glacier, hasCamp, base camp for Khan Tengri ascents]
-
A.
hasCampType
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
B.
hadCamp
Indicates that an entity conducted, hosted, or participated in a camp event or camping activity.
-
C.
hasCampground
chosen
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
hasCampusFeature
Indicates that a campus possesses or includes a specific physical or functional feature.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a940c048190bc46e2c8001db8c0 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.