Triple
T12605618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uturuncu |
E300970
|
entity |
| Predicate | upliftRate |
P105662
|
FINISHED |
| Object | on the order of 1–2 cm per year |
—
|
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: on the order of 1–2 cm per year | Statement: [Uturuncu, upliftRate, on the order of 1–2 cm per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upliftRate Context triple: [Uturuncu, upliftRate, on the order of 1–2 cm per year]
-
A.
increasedRateOn
Indicates that one entity has raised the rate, fee, or charge applied to another entity.
-
B.
hasHighestLift
Indicates that the subject entity achieves the greatest lift value (e.g., improvement or elevation relative to a baseline) compared to all other relevant entities in the given context.
-
C.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
D.
upgradeable
Indicates that an entity can be improved or enhanced to a higher version, level, or capability.
-
E.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence or process.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95590a5e08190842b988531cf2921 |
completed | April 10, 2026, 7:54 p.m. |
Created at: April 9, 2026, 5:10 p.m.