Triple
T4229071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotlum Glacier |
E94532
|
entity |
| Predicate | drainsDirection |
P8846
|
FINISHED |
| Object | northeast |
—
|
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: northeast | Statement: [Hotlum Glacier, drainsDirection, northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsDirection Context triple: [Hotlum Glacier, drainsDirection, northeast]
-
A.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
B.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
C.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
D.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
E.
drainagePattern
Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e51817c8190bff50f2c3b5deea0 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.