Triple
T3236075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhine–Main–Danube Canal |
E67857
|
entity |
| Predicate | openedForNavigation |
P23654
|
FINISHED |
| Object | September 1992 |
—
|
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: September 1992 | Statement: [Rhine–Main–Danube Canal, openedForNavigation, September 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForNavigation Context triple: [Rhine–Main–Danube Canal, openedForNavigation, September 1992]
-
A.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
B.
reopenedForNavigation
Indicates that something previously closed to traffic or passage has been opened again for navigational use.
-
C.
openedRouteThrough
chosen
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
openedAfter
Indicates that one entity was opened at a later time than another entity.
-
E.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaee05d34819095dbce4db6ac8613 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.