Triple
T7268283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Glacier |
E161033
|
entity |
| Predicate | hasIceFlowDirection |
P8846
|
FINISHED |
| Object | generally southward toward Prince William Sound |
—
|
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: generally southward toward Prince William Sound | Statement: [Columbia Glacier, hasIceFlowDirection, generally southward toward Prince William Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceFlowDirection Context triple: [Columbia Glacier, hasIceFlowDirection, generally southward toward Prince William Sound]
-
A.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
B.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
D.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
E.
glacierFlowRate
Indicates the rate at which a glacier moves or flows over a given distance in a specified 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.