Triple
T24051915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beuel-Mitte |
E595681
|
entity |
| Predicate | riverCrossingAccess |
P33399
|
FINISHED |
| Object | Kennedybrücke (Bonn) via Beuel side |
—
|
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: Kennedybrücke (Bonn) via Beuel side | Statement: [Beuel-Mitte, riverCrossingAccess, Kennedybrücke (Bonn) via Beuel side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingAccess Context triple: [Beuel-Mitte, riverCrossingAccess, Kennedybrücke (Bonn) via Beuel side]
-
A.
waterwayAccess
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
-
B.
hasRiverCrossingType
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
-
C.
riverCrossingConnection
chosen
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
D.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
E.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d32f3c8190b48a77c844f4df8e |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:21 p.m.