Triple
T25436771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee River |
E637393
|
entity |
| Predicate | emptiesIntoVia |
P408
|
FINISHED |
| Object | Mount Hope Bay |
—
|
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: Mount Hope Bay | Statement: [Lee River, emptiesIntoVia, Mount Hope Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emptiesIntoVia Context triple: [Lee River, emptiesIntoVia, Mount Hope Bay]
-
A.
emptiesInto
chosen
Indicates that one entity serves as the destination or outlet into which another entity flows, discharges, or is emptied.
-
B.
historicallyEmptiedInto
Indicates that a body of water or watercourse previously discharged its flow into another body of water or location in the past, though this outflow may have since changed.
-
C.
drainedIn
Indicates that a liquid, resource, or substance has flowed out from one entity and been discharged or emptied into another entity or location.
-
D.
drainsPartOf
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
E.
drainedFrom
Indicates that a substance, resource, or liquid has been removed or emptied out from a particular source or container.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e0338c8190ace22e7a6239f68d |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:59 p.m.