Triple
T24960470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byrd Glacier system |
E624591
|
entity |
| Predicate | channelsIceTo |
P48173
|
FINISHED |
| Object | Ross Ice Shelf |
—
|
NE NERFINISHED |
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: Ross Ice Shelf | Statement: [Byrd Glacier system, channelsIceTo, Ross Ice Shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelsIceTo Context triple: [Byrd Glacier system, channelsIceTo, Ross Ice Shelf]
-
A.
channels
chosen
Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
-
B.
iceCapability
Indicates that an entity has the ability or functional capacity to produce, manage, or utilize ice.
-
C.
iceFeature
Indicates a relationship where a geographic or environmental feature is composed of, covered by, or characterized by ice.
-
D.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
-
E.
iceClass
Indicates a classification relationship specifying the level or category of ice-strengthening or ice-navigation capability assigned to a vessel or structure.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242c447c8190bf7972390ac93814 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:58 a.m.