Triple
T24052221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennedy Bridge (Bonn) |
E595690
|
entity |
| Predicate | linksBank |
P154677
|
FINISHED |
| Object | right bank of Rhine |
—
|
LITERAL 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: right bank of Rhine | Statement: [Kennedy Bridge (Bonn), linksBank, right bank of Rhine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksBank Context triple: [Kennedy Bridge (Bonn), linksBank, right bank of Rhine]
-
A.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
B.
banksOften
Indicates that the subject frequently or habitually engages in banking activities with the object (such as depositing, withdrawing, or otherwise using banking services).
-
C.
trackBanking
Indicates monitoring, recording, or managing banking-related activities or transactions associated with an entity.
-
D.
bankSection
Indicates a specific part or division within a bank that is associated with or relevant to the related entity.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river 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_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. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:21 p.m.