Triple
T33616436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hintereisferner |
E861130
|
entity |
| Predicate | lengthChangeMonitoringSince |
P9992
|
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, lengthChangeMonitoringSince, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthChangeMonitoringSince Context triple: [Hintereisferner, lengthChangeMonitoringSince, late 19th century]
-
A.
previousTermLengthChangedIn
Indicates that the duration or length of the immediately preceding term has been modified within a specified context or period.
-
B.
observedSince
chosen
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
C.
historicalLength
Indicates the duration or extent of time over which something has existed, occurred, or been recorded in the past.
-
D.
laterModifiedInPeriod
Indicates that one entity was modified at a later time than another entity within the same defined time period.
-
E.
distanceChangeHistory
Indicates how the distance between entities has varied over time, capturing a record of past distance changes.
- 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_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. |
Created at: May 1, 2026, 1:41 a.m.