Triple
T6843533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klyazma River |
E157834
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object |
Peksha River
The Peksha River is a smaller waterway in central Russia that feeds into the larger Klyazma River within the Volga basin.
|
E835303
|
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: Peksha River | Statement: [Klyazma River, hasTributary, Peksha River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peksha River Context triple: [Klyazma River, hasTributary, Peksha River]
-
A.
Pokshenga River
The Pokshenga River is a waterway in northern Russia that feeds into the larger Northern Dvina River system.
-
B.
Muksu River
The Muksu River is a glacially fed mountain river in Tajikistan that flows through the Pamir-Alay ranges and forms one of the main headwaters of the Vakhsh River.
-
C.
Sasanoa River
The Sasanoa River is a tidal waterway in coastal Maine that connects the Kennebec and Sheepscot rivers, forming part of an important inland navigation route.
-
D.
Kuitun River
The Kuitun River is a river in Xinjiang, China, that serves as one of the main tributaries feeding Ebinur Lake in the region’s arid northwest.
-
E.
Mulmuga River
The Mulmuga River is a significant watercourse in Russia's Far East that feeds into the larger Zeya River system.
- 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: Peksha River Triple: [Klyazma River, hasTributary, Peksha River]
Generated description
The Peksha River is a smaller waterway in central Russia that feeds into the larger Klyazma River within the Volga basin.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Peksha River Target entity description: The Peksha River is a smaller waterway in central Russia that feeds into the larger Klyazma River within the Volga basin.
-
A.
Pokshenga River
The Pokshenga River is a waterway in northern Russia that feeds into the larger Northern Dvina River system.
-
B.
Muksu River
The Muksu River is a glacially fed mountain river in Tajikistan that flows through the Pamir-Alay ranges and forms one of the main headwaters of the Vakhsh River.
-
C.
Sasanoa River
The Sasanoa River is a tidal waterway in coastal Maine that connects the Kennebec and Sheepscot rivers, forming part of an important inland navigation route.
-
D.
Kuitun River
The Kuitun River is a river in Xinjiang, China, that serves as one of the main tributaries feeding Ebinur Lake in the region’s arid northwest.
-
E.
Mulmuga River
The Mulmuga River is a significant watercourse in Russia's Far East that feeds into the larger Zeya River system.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b7179481909e3482fef47b2719 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2693f054081909fe58a252bd76226 |
completed | April 5, 2026, 1:53 p.m. |
| NEDg | Description generation | batch_69d26db507e08190b0a94e6c3730ec19 |
completed | April 5, 2026, 2:12 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d26e108a588190b8cdb9a496d07a82 |
completed | April 5, 2026, 2:13 p.m. |
Created at: March 27, 2026, 2:19 p.m.