Triple
T9540409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regen |
E230141
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object |
Regen (river)
The Regen is a river in Bavaria, Germany, that flows through the Bavarian Forest and joins the Danube near Regensburg.
|
E805355
|
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: Regen (river) | Statement: [Regen, locatedOnRiver, Regen (river)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regen (river) Context triple: [Regen, locatedOnRiver, Regen (river)]
-
A.
Rega River
The Rega River is a river in northwestern Poland that flows through the West Pomeranian region into the Baltic Sea.
-
B.
Drangme River
Drangme River is a major river in eastern Bhutan that flows through deep valleys and gorges before joining other rivers to form the Manas River system.
-
C.
Zergan River
The Zergan River is a tributary watercourse in the Middle East that feeds into the Khabur River, contributing to the hydrology of the upper Euphrates basin.
-
D.
Berach River
The Berach River is a significant river in the Indian state of Rajasthan that flows through the Mewar region and ultimately joins the Banas River.
-
E.
Ruza River
The Ruza River is a waterway in western Russia that serves as one of the tributaries feeding into the Moskva River.
- 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: Regen (river) Triple: [Regen, locatedOnRiver, Regen (river)]
Generated description
The Regen is a river in Bavaria, Germany, that flows through the Bavarian Forest and joins the Danube near Regensburg.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Regen (river) Target entity description: The Regen is a river in Bavaria, Germany, that flows through the Bavarian Forest and joins the Danube near Regensburg.
-
A.
Rega River
The Rega River is a river in northwestern Poland that flows through the West Pomeranian region into the Baltic Sea.
-
B.
Drangme River
Drangme River is a major river in eastern Bhutan that flows through deep valleys and gorges before joining other rivers to form the Manas River system.
-
C.
Zergan River
The Zergan River is a tributary watercourse in the Middle East that feeds into the Khabur River, contributing to the hydrology of the upper Euphrates basin.
-
D.
Berach River
The Berach River is a significant river in the Indian state of Rajasthan that flows through the Mewar region and ultimately joins the Banas River.
-
E.
Ruza River
The Ruza River is a waterway in western Russia that serves as one of the tributaries feeding into the Moskva River.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14c5da5a081909d646c69d5de8e18 |
completed | April 4, 2026, 5:37 p.m. |
| NEDg | Description generation | batch_69d14d0c39c88190a705470104dc7b80 |
completed | April 4, 2026, 5:40 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d14d79065081908a4e619c71e0d359 |
completed | April 4, 2026, 5:42 p.m. |
Created at: March 30, 2026, 8:01 p.m.