Triple
T10600783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuptse |
E275739
|
entity |
| Predicate | ridgeOrientation |
P39424
|
FINISHED |
| Object | west-east |
—
|
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: west-east | Statement: [Nuptse, ridgeOrientation, west-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ridgeOrientation Context triple: [Nuptse, ridgeOrientation, west-east]
-
A.
gateOrientation
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
B.
ridgeAxis
chosen
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
C.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
D.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
E.
orientationOfCross
Indicates the spatial orientation or alignment of a cross relative to a reference frame or object.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:31 p.m.