Triple
T4236933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ismoil Somoni Peak |
E94715
|
entity |
| Predicate | relativeHeightCategory |
P54862
|
FINISHED |
| Object | ultra-prominent peak |
—
|
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: ultra-prominent peak | Statement: [Ismoil Somoni Peak, relativeHeightCategory, ultra-prominent peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeightCategory Context triple: [Ismoil Somoni Peak, relativeHeightCategory, ultra-prominent peak]
-
A.
heightClass
Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
-
B.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
E.
relativeHeightAboveCity
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e7422a88190955f5f4347fa80d2 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.