Triple
T11439487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Pyramid |
E271103
|
entity |
| Predicate | belowFeature |
P24809
|
FINISHED |
| Object | Shoulder of K2 |
—
|
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: Shoulder of K2 | Statement: [Black Pyramid, belowFeature, Shoulder of K2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belowFeature Context triple: [Black Pyramid, belowFeature, Shoulder of K2]
-
A.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
B.
liesBelow
chosen
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
D.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
E.
bottomType
Indicates that the subject entity is classified as a bottom-level or most specific type within a type hierarchy.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.