Triple
T26774748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoup Bay |
E670086
|
entity |
| Predicate | receivesIceFrom |
P48630
|
FINISHED |
| Object | Shoup Glacier |
—
|
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: Shoup Glacier | Statement: [Shoup Bay, receivesIceFrom, Shoup Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesIceFrom Context triple: [Shoup Bay, receivesIceFrom, Shoup Glacier]
-
A.
receivesIcebergsFrom
Indicates that one entity is the source or destination in a process where it obtains or is supplied with icebergs from another entity.
-
B.
iceCapability
Indicates that an entity has the ability or functional capacity to produce, manage, or utilize ice.
-
C.
hasIceSource
chosen
Indicates that one entity serves as the origin or provider of ice for another entity.
-
D.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
E.
receiverInterface
Indicates that one entity functions as the receiving interface or endpoint for communications, signals, or data originating from another entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 4:04 a.m.