Triple
T33128588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Lawrence canals system |
E847789
|
entity |
| Predicate | navigationDirection |
P24810
|
FINISHED |
| Object | upbound and downbound shipping |
—
|
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: upbound and downbound shipping | Statement: [St. Lawrence canals system, navigationDirection, upbound and downbound shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationDirection Context triple: [St. Lawrence canals system, navigationDirection, upbound and downbound shipping]
-
A.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
B.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
C.
navigationControlBy
Indicates that one entity directs, manages, or influences the navigation or movement of another entity.
-
D.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
E.
transportDirection
chosen
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.