Triple
T2281172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Shore of the Saint Lawrence River |
E51281
|
entity |
| Predicate | isNavigationCorridorFor |
P3034
|
FINISHED |
| Object | ocean-going vessels |
—
|
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: ocean-going vessels | Statement: [North Shore of the Saint Lawrence River, isNavigationCorridorFor, ocean-going vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigationCorridorFor Context triple: [North Shore of the Saint Lawrence River, isNavigationCorridorFor, ocean-going vessels]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
-
C.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
E.
transportCorridor
chosen
Indicates a route or pathway used to move people, goods, or resources between locations.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21c405881908c4df7bee36136fe |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.