Triple
T5691717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwestern Ohio |
E125440
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Mad River |
E64845
|
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: Mad River | Statement: [Southwestern Ohio, hasRiver, Mad River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mad River Context triple: [Southwestern Ohio, hasRiver, Mad River]
-
A.
Mad River
chosen
Mad River is a tributary of the Great Miami River in western Ohio known for its clear, cold waters and popularity for fishing and paddling.
-
B.
Mad River
Mad River is a waterway in northwestern California that flows through the ancestral lands of the Wiyot people before emptying into the Pacific Ocean.
-
C.
Mad River
Mad River is a tributary stream in New Hampshire that feeds into the Pemigewasset River within the Merrimack River watershed.
-
D.
Waters River
Waters River is a small waterway in Massachusetts that flows through the town of Danvers.
-
E.
Mad River (Vermont)
Mad River (Vermont) is a scenic mountain river in central Vermont known for its clear waters, popular trout fishing, and role in regional outdoor recreation.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c023e500ec8190bfda4f6a818aa5dc |
completed | March 22, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c91b0ad9188190ad74c33802f50783 |
completed | March 29, 2026, 12:28 p.m. |
Created at: March 22, 2026, 3:44 p.m.