Triple
T26117294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunda Strait region |
E658855
|
entity |
| Predicate | shippingConstraint |
P33452
|
FINISHED |
| Object | narrow passages |
—
|
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: narrow passages | Statement: [Sunda Strait region, shippingConstraint, narrow passages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingConstraint Context triple: [Sunda Strait region, shippingConstraint, narrow passages]
-
A.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
B.
transportRestriction
chosen
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
C.
shippingLine
Indicates a relationship where an entity is associated with, or transported via, a particular shipping line or carrier service.
-
D.
shippingLaneFor
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).
-
E.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60ac86d908190bf582de7891fb4b3 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:06 p.m.