Triple
T11801086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komandorski Islands |
E280625
|
entity |
| Predicate | shippingContext |
P84718
|
FINISHED |
| Object | Bering Sea shipping routes |
—
|
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: Bering Sea shipping routes | Statement: [Komandorski Islands, shippingContext, Bering Sea shipping routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingContext Context triple: [Komandorski Islands, shippingContext, Bering Sea shipping routes]
-
A.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
B.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
C.
shippingLaneFor
chosen
Indicates that one entity serves as a designated shipping lane or route used for the transportation or navigation of another entity (such as ships or cargo).
-
D.
stateShip
Indicates that a ship is officially registered, documented, or associated with a particular state or governmental authority.
-
E.
protectsShippingTo
Indicates that one entity safeguards or ensures the security of shipping or delivery directed toward another entity.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.