Triple
T13391200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock River |
E319574
|
entity |
| Predicate | hasMajorTributary |
P415
|
FINISHED |
| Object |
Sugar River
Sugar River is a tributary waterway in the Midwestern United States that flows through southern Wisconsin and northern Illinois before joining the Rock River.
|
E1249261
|
NE FINISHED |
How this triple was built (4 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: Sugar River | Statement: [Rock River, hasMajorTributary, Sugar River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sugar River Context triple: [Rock River, hasMajorTributary, Sugar River]
-
A.
Sugar River
Sugar River is a New Hampshire river that drains Lake Sunapee and flows westward to join the Connecticut River.
-
B.
Mad River
Mad River is a tributary stream in New Hampshire that feeds into the Pemigewasset River within the Merrimack River watershed.
-
C.
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.
-
D.
Mad River
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.
-
E.
Waters River
Waters River is a small waterway in Massachusetts that flows through the town of Danvers.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sugar River Triple: [Rock River, hasMajorTributary, Sugar River]
Generated description
Sugar River is a tributary waterway in the Midwestern United States that flows through southern Wisconsin and northern Illinois before joining the Rock River.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sugar River Target entity description: Sugar River is a tributary waterway in the Midwestern United States that flows through southern Wisconsin and northern Illinois before joining the Rock River.
-
A.
Sugar River
Sugar River is a New Hampshire river that drains Lake Sunapee and flows westward to join the Connecticut River.
-
B.
Mad River
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.
-
C.
Mad River
Mad River is a tributary stream in New Hampshire that feeds into the Pemigewasset River within the Merrimack River watershed.
-
D.
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.
-
E.
Waters River
Waters River is a small waterway in Massachusetts that flows through the town of Danvers.
- F. None of above. chosen
Provenance (5 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d543348190a9c1be509b015c0f |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ec19c508190912c3fe186f8a992 |
completed | May 11, 2026, 1:20 a.m. |
| NEDg | Description generation | batch_6a01313d46908190a8e6df35a4bcf7e8 |
completed | May 11, 2026, 1:30 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a013198d2d08190b593694809ac2ad6 |
completed | May 11, 2026, 1:32 a.m. |
Created at: April 9, 2026, 9:34 p.m.