Triple
T21495006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoldia stage |
E530327
|
entity |
| Predicate | hasOriginProcess |
P1410
|
FINISHED |
| Object | retreat of continental ice sheets |
—
|
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: retreat of continental ice sheets | Statement: [Yoldia stage, hasOriginProcess, retreat of continental ice sheets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginProcess Context triple: [Yoldia stage, hasOriginProcess, retreat of continental ice sheets]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
C.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
D.
hasPrimaryVisitorOrigin
Indicates that an entity’s main or most common source location of its visitors is a specified place.
-
E.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea575f2c81909cc0607c4b529f8d |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.