Triple
T4658692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ötztal |
E102473
|
entity |
| Predicate | highestAreasFeature |
P12635
|
FINISHED |
| Object | glaciers |
—
|
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: glaciers | Statement: [Ötztal, highestAreasFeature, glaciers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestAreasFeature Context triple: [Ötztal, highestAreasFeature, glaciers]
-
A.
hasLargestAreaOf
Indicates that the subject entity possesses the greatest area (size of surface or region) compared to the other entities in the specified set or context.
-
B.
largestNeighborhoodByArea
Indicates the relationship where a neighborhood is identified as the one with the greatest land area among a specified set or within a given region.
-
C.
arealFeature
chosen
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
D.
hasLandmarkArea
Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
-
E.
featuredArea
Indicates that an area or section is highlighted or given special prominence within a larger context or layout.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd63271a548190bd9662b69a45d9a5 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.