Triple
T13482095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven-thousanders of the Tian Shan |
E318395
|
entity |
| Predicate | containsPeakAbove |
P105025
|
FINISHED |
| Object | 7000 metres |
—
|
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: 7000 metres | Statement: [Seven-thousanders of the Tian Shan, containsPeakAbove, 7000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPeakAbove Context triple: [Seven-thousanders of the Tian Shan, containsPeakAbove, 7000 metres]
-
A.
hasPeakOver
chosen
Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
-
B.
hasPeakAround
Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
-
C.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
D.
hasSharperPeakThan
Indicates that one entity’s peak (e.g., in a graph, distribution, or signal) is more pointed or narrow than the peak of another entity.
-
E.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.