Triple
T12737814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom St. Bartholomäus |
E304408
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Main River |
E113003
|
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: Main River | Statement: [Dom St. Bartholomäus, locatedNear, Main River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Main River Context triple: [Dom St. Bartholomäus, locatedNear, Main River]
-
A.
You River
The You River is a tributary waterway in southern China that feeds into the larger Yuan River system.
-
B.
River Main
chosen
The River Main is a major waterway in central Germany that flows through cities such as Frankfurt before joining the Rhine.
-
C.
Kako River
The Kako River is a river in Japan whose name was used for the Imperial Japanese Navy cruiser Kako.
-
D.
Sure river
The Sure river is a Swiss watercourse that drains Lake Sempach and flows through the canton of Lucerne before joining larger river systems.
-
E.
Emme River
The Emme River is a Swiss river flowing through the Emmental region and the Swiss Plateau, known for its picturesque valleys and historical flooding events.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9646cfcac81909283dca987755c0e |
completed | April 10, 2026, 8:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c8ff57c8190a935b5c9f4bb5aa3 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.