Triple
T30752071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randers Fjord |
E782980
|
entity |
| Predicate | isNavigationRouteTo |
P53909
|
FINISHED |
| Object | Port of Randers |
—
|
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: Port of Randers | Statement: [Randers Fjord, isNavigationRouteTo, Port of Randers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigationRouteTo Context triple: [Randers Fjord, isNavigationRouteTo, Port of Randers]
-
A.
hasNavigationRoute
chosen
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
B.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
C.
isOnNavigation
Indicates that one entity is currently located on, or actively using, a navigation interface, route, or control associated with another entity.
-
D.
isNavigationStar
Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
-
E.
isNavigableVia
Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f91f0cc8190936582859f7d1683 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.