Triple
T27453749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reeves Glacier |
E692524
|
entity |
| Predicate | flowsIntoSide |
P84939
|
FINISHED |
| Object | western side of Terra Nova Bay |
—
|
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: western side of Terra Nova Bay | Statement: [Reeves Glacier, flowsIntoSide, western side of Terra Nova Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoSide Context triple: [Reeves Glacier, flowsIntoSide, western side of Terra Nova Bay]
-
A.
flowsUltimatelyInto
Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
-
B.
flowsDownSideOf
chosen
Indicates that one entity moves or runs downward along the side or surface of another entity.
-
C.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsBeside
Indicates that one entity moves or runs alongside another entity in close proximity without crossing or intersecting it.
-
E.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:48 p.m.