Triple
T26818154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barents–Kara Ice Sheet |
E675172
|
entity |
| Predicate | leftBehind |
P162181
|
FINISHED |
| Object | glacial lineations |
—
|
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 lineations | Statement: [Barents–Kara Ice Sheet, leftBehind, glacial lineations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftBehind Context triple: [Barents–Kara Ice Sheet, leftBehind, glacial lineations]
-
A.
leftBehind
chosen
Indicates that one entity remains in a place or situation after another entity has departed or moved on.
-
B.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
C.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
D.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
E.
خلفه
Indicates that one entity comes after, succeeds, or replaces another in position, role, or time.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:53 a.m.