Triple
T23953055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шхара |
E603101
|
entity |
| Predicate | имеетТипРельефа |
P80940
|
FINISHED |
| Object | альпийский |
—
|
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: альпийский | Statement: [Шхара, имеетТипРельефа, альпийский]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетТипРельефа Context triple: [Шхара, имеетТипРельефа, альпийский]
-
A.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
B.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
D.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
E.
topographicalCategory
chosen
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.