Triple
T1161560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwan Strait |
E24502
|
entity |
| Predicate | hasShippingLane |
P2855
|
FINISHED |
| Object | major international shipping route |
—
|
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: major international shipping route | Statement: [Taiwan Strait, hasShippingLane, major international shipping route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShippingLane Context triple: [Taiwan Strait, hasShippingLane, major international shipping route]
-
A.
containsShippingRoute
chosen
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
B.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
C.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
E.
shippingFunction
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.