Triple
T6491812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keene, New York |
E148056
|
entity |
| Predicate | hasNaturalFeature |
P1094
|
FINISHED |
| Object | Ausable River |
E255694
|
NE 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: Ausable River | Statement: [Keene, New York, hasNaturalFeature, Ausable River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ausable River Context triple: [Keene, New York, hasNaturalFeature, Ausable River]
-
A.
Ausable River
chosen
The Ausable River is a scenic mountain river in northeastern New York known for its deep gorges, waterfalls, and popular trout fishing within the Adirondack region.
-
B.
Beaver River
Beaver River is a waterway in western Pennsylvania that flows through Beaver County and ultimately joins the Ohio River.
-
C.
Beaver River
Beaver River is a tributary waterway in Utah that flows through Beaver County before joining the Sevier River.
-
D.
Beaver River
Beaver River is a significant waterway in the Oklahoma Panhandle that forms part of the upper course of the North Canadian River.
-
E.
Clear River
Clear River is a Canadian waterway that serves as a tributary of the Peace River within the Peace River watershed.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9bf9208190b0957eda06ed3d65 |
completed | March 22, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f4a2bd881909745f349d847ca87 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 22, 2026, 4:53 p.m.