Triple
T8808667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosario Strait |
E209598
|
entity |
| Predicate | shippingLaneFor |
P84718
|
FINISHED |
| Object | commercial 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: commercial vessels | Statement: [Rosario Strait, shippingLaneFor, commercial vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingLaneFor Context triple: [Rosario Strait, shippingLaneFor, commercial vessels]
-
A.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
-
B.
shippingLaneStatus
Indicates the current operational condition or availability of a specified shipping lane for transit or navigation.
-
C.
ownedShippingLine
Indicates that one entity possessed legal ownership or controlling interest in a particular shipping line.
-
D.
shippingLaneImportance
Indicates the degree to which a particular shipping lane is considered significant or critical relative to other possible routes.
-
E.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
- F. None of above. chosen
Provenance (4 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd4cbec8190a929d4e60da8ad65 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.