Triple
T24135874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rüngsdorf |
E598084
|
entity |
| Predicate | locatedOppositeAcrossRhineFrom |
P154975
|
FINISHED |
| Object | Königswinter |
—
|
NE NERFINISHED |
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: Königswinter | Statement: [Rüngsdorf, locatedOppositeAcrossRhineFrom, Königswinter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOppositeAcrossRhineFrom Context triple: [Rüngsdorf, locatedOppositeAcrossRhineFrom, Königswinter]
-
A.
hasNeighbouringCountryAcrossRhine
Indicates that one country is geographically adjacent to another with the Rhine River forming or crossing their shared border.
-
B.
hasCountryOnBothBanks
Indicates that a river or waterway has the same country located on both of its banks along the relevant segment.
-
C.
hasCountryOnRightBank
Indicates that a specified country is located on the right bank of a given river or watercourse.
-
D.
hasCityOnRightBank
Indicates that a city is located on the right bank of a specified river or watercourse.
-
E.
oppositeTownAcrossRhône
Indicates that one town is located directly across the Rhône River from another town, on the opposite bank.
- F. None of above. chosen
Provenance (4 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7c3ce08190bcbd9056a6630c2f |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:27 p.m.