Triple
T17810894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Horse Creek |
E444699
|
entity |
| Predicate | hasMouthIn |
P1008
|
FINISHED |
| Object | Pages River |
—
|
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: Pages River | Statement: [Dead Horse Creek, hasMouthIn, Pages River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pages River Context triple: [Dead Horse Creek, hasMouthIn, Pages River]
-
A.
Pages River
chosen
Pages River is a minor river in New South Wales, Australia, that forms part of the Hunter River catchment.
-
B.
Ourthe River
The Ourthe River is a major watercourse in southeastern Belgium that flows through the Ardennes region before joining the Meuse River.
-
C.
Days River
Days River is a river in Michigan’s Upper Peninsula that flows into Little Bay de Noc on Lake Michigan.
-
D.
Or River
The Or River is a waterway in Russia and Kazakhstan that flows through the southern Ural region before joining the Ural River.
-
E.
River Brain
The River Brain is a small river in Essex, England, that serves as a tributary of the River Blackwater and flows through the town of Witham.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887b5e50819098506f0b92d709b5 |
completed | April 19, 2026, 7:47 a.m. |
Created at: April 10, 2026, 10:14 a.m.