Triple
T6724867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hay Point |
E153490
|
entity |
| Predicate | shippingRoute |
P2855
|
FINISHED |
| Object | Asia-Pacific coal trade 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: Asia-Pacific coal trade routes | Statement: [Hay Point, shippingRoute, Asia-Pacific coal trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingRoute Context triple: [Hay Point, shippingRoute, Asia-Pacific coal trade routes]
-
A.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
B.
containsShippingRoute
chosen
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
C.
stateShip
Indicates that a ship is officially registered, documented, or associated with a particular state or governmental authority.
-
D.
protectsShippingTo
Indicates that one entity safeguards or ensures the security of shipping or delivery directed toward another entity.
-
E.
ownedShippingLine
Indicates that one entity possessed legal ownership or controlling interest in a particular shipping line.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.