Triple
T9540630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regen (district) |
E230146
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Regen (river) |
E805355
|
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: Regen (river) | Statement: [Regen (district), namedAfter, Regen (river)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regen (river) Context triple: [Regen (district), namedAfter, Regen (river)]
-
A.
Regen (river)
chosen
The Regen is a river in Bavaria, Germany, that flows through the Bavarian Forest and joins the Danube near Regensburg.
-
B.
Rega River
The Rega River is a river in northwestern Poland that flows through the West Pomeranian region into the Baltic Sea.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_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_69d15278efd4819091e707aabd9a59d7 |
completed | April 4, 2026, 6:03 p.m. |
Created at: March 30, 2026, 8:01 p.m.