Triple
T2611803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muztagh Tower |
E58790
|
entity |
| Predicate | secondAscentSide |
P5443
|
FINISHED |
| Object | Chinese side |
—
|
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: Chinese side | Statement: [Muztagh Tower, secondAscentSide, Chinese side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondAscentSide Context triple: [Muztagh Tower, secondAscentSide, Chinese side]
-
A.
firstAscentFromSide
Indicates that an ascent was the first recorded climb of a peak specifically via a particular side or face.
-
B.
side2
chosen
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
C.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
D.
firstAscentFrom
Indicates the starting location or route from which the first successful ascent of something (typically a peak or climb) was made.
-
E.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.