Triple
T27403149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carstensz Glacier |
E691912
|
entity |
| Predicate | isRapidlyShrinking |
P162384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Carstensz Glacier, isRapidlyShrinking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRapidlyShrinking Context triple: [Carstensz Glacier, isRapidlyShrinking, true]
-
A.
dieShrinkOf
Indicates that one entity is a smaller, more advanced manufacturing process node derived from the other entity’s larger, earlier process node.
-
B.
dieShrinkOf
Indicates that one entity is a smaller, more advanced manufacturing process node derived from another, larger process node.
-
C.
isResourcePoor
Indicates that an entity lacks sufficient resources (such as money, materials, or capacity) to meet its needs or perform effectively.
-
D.
isFastGrowing
Indicates that an entity increases in size, quantity, or impact at a rapid or above-average rate over time.
-
E.
expandedRapidly
Indicates that an entity’s size, scope, or intensity increased significantly within a short period of time.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd4bd80819081454e99c3eec5a9 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:30 p.m.