Triple
T33616434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hintereisferner |
E861130
|
entity |
| Predicate | monitoringSince |
P176962
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Hintereisferner, monitoringSince, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoringSince Context triple: [Hintereisferner, monitoringSince, late 19th century]
-
A.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
B.
monitoringLevel
Indicates the degree or intensity with which an entity is observed, tracked, or supervised over time.
-
C.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
D.
monitoringBodyEstablishedOn
Indicates that a monitoring body was formally created or instituted on a specific date.
-
E.
monitoringBody
Indicates that one entity is responsible for overseeing, supervising, or tracking the activities, performance, or compliance of another entity.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f817bc888190939e060506dca59a |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.