Triple
T2946553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furtwängler Glacier |
E79515
|
entity |
| Predicate | hasAreaTrend |
P5318
|
FINISHED |
| Object | decreasing |
—
|
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: decreasing | Statement: [Furtwängler Glacier, hasAreaTrend, decreasing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAreaTrend Context triple: [Furtwängler Glacier, hasAreaTrend, decreasing]
-
A.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasLandmarkArea
Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
-
D.
catchmentArea
Indicates the geographic area from which something (such as a facility, service, or natural feature) draws or collects people, resources, or water.
-
E.
hasTendency
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b3f86c819094526c2af611bfb5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.