Triple
T36995749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sieg |
E915222
|
entity |
| Predicate | confluenceWithRhineNear |
P157273
|
FINISHED |
| Object | Bonn |
—
|
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: Bonn | Statement: [Sieg, confluenceWithRhineNear, Bonn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confluenceWithRhineNear Context triple: [Sieg, confluenceWithRhineNear, Bonn]
-
A.
locatedOppositeAcrossRhineFrom
Indicates that one entity is situated on the other side of the Rhine River directly facing or across from the referenced entity.
-
B.
heightAboveRhine
Indicates the vertical elevation of an entity relative to the water level of the Rhine River.
-
C.
hasNeighbouringCountryAcrossRhine
Indicates that one country is geographically adjacent to another with the Rhine River forming or crossing their shared border.
-
D.
confluenceWith
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
E.
joinsRiverNear
chosen
Indicates that one river or watercourse flows into and merges with another river at or close to a specified location.
- F. None of above.
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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.