Triple
T5415556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fennoscandian Ice Sheet |
E121119
|
entity |
| Predicate | causedProcess |
P38222
|
FINISHED |
| Object | glacial isostatic adjustment |
—
|
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: glacial isostatic adjustment | Statement: [Fennoscandian Ice Sheet, causedProcess, glacial isostatic adjustment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causedProcess Context triple: [Fennoscandian Ice Sheet, causedProcess, glacial isostatic adjustment]
-
A.
createdProcess
chosen
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
B.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
D.
originProcess
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
-
E.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87be754c81909c0d0df6216cae46 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.