Triple
T24960473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byrd Glacier system |
E624591
|
entity |
| Predicate | hasMainOutletGlacier |
P98289
|
FINISHED |
| Object | Byrd 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: Byrd Glacier | Statement: [Byrd Glacier system, hasMainOutletGlacier, Byrd Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainOutletGlacier Context triple: [Byrd Glacier system, hasMainOutletGlacier, Byrd Glacier]
-
A.
hasGlacierOutlet
chosen
Indicates that a glacier has a specific outlet feature or location through which its ice or meltwater flows or exits.
-
B.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
C.
isGlaciallyFed
Indicates that something (typically a body of water) receives its primary input or supply from melting glacial ice.
-
D.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
-
E.
hasGlacierArm
Indicates that a glacier possesses or extends into a subsidiary arm or branch of ice connected to it.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 5:58 a.m.