Triple
T2673123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Bight |
E56393
|
entity |
| Predicate | hasShippingLaneType |
P41609
|
FINISHED |
| Object | international shipping lanes |
—
|
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: international shipping lanes | Statement: [New York Bight, hasShippingLaneType, international shipping lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShippingLaneType Context triple: [New York Bight, hasShippingLaneType, international shipping lanes]
-
A.
containsShippingRoute
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
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.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
E.
isKeyFreightRoute
Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b08b1c8190824342fc63e555d2 |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.