Triple
T36161708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube at Komárno |
E1045895
|
entity |
| Predicate | isKeyJunctionIn |
P182111
|
FINISHED |
| Object | regional river transport |
—
|
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: regional river transport | Statement: [Danube at Komárno, isKeyJunctionIn, regional river transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyJunctionIn Context triple: [Danube at Komárno, isKeyJunctionIn, regional river transport]
-
A.
isJunction
Indicates that an entity functions as a junction point where multiple paths, lines, or connections meet or intersect.
-
B.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
C.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
D.
isKeyConnectionPointFor
Indicates that something serves as a primary or critical linking point that connects or integrates other elements within a system or structure.
-
E.
isKeyTransitPointOn
chosen
Indicates that a location serves as a major or critical transfer or passage point along a specified route, corridor, or network.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.