Triple
T9025307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade Bay region |
E216031
|
entity |
| Predicate | shippingAccess |
P85917
|
FINISHED |
| Object | deep-water access independent of tides |
—
|
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: deep-water access independent of tides | Statement: [Jade Bay region, shippingAccess, deep-water access independent of tides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingAccess Context triple: [Jade Bay region, shippingAccess, deep-water access independent of tides]
-
A.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
B.
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).
-
C.
stateShip
Indicates that a ship is officially registered, documented, or associated with a particular state or governmental authority.
-
D.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
E.
shippingRisk
Indicates the level or likelihood of potential loss, damage, or delay associated with transporting goods from one location to another.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7b902c81909fcbdc433a1acf7a |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.