Triple

T1143863
Position Surface form Disambiguated ID Type / Status
Subject Java Sea E23517 entity
Predicate shippingRole P2855 FINISHED
Object link between Java Sea ports and global 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: link between Java Sea ports and global trade routes | Statement: [Java Sea, shippingRole, link between Java Sea ports and global trade routes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shippingRole
Context triple: [Java Sea, shippingRole, link between Java Sea ports and global 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. hasCargoServices
    Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
  • D. deliveredBy
    Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
  • E. hasShip
    Indicates that one entity possesses, owns, or is equipped with a ship.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc5008d8819095c1ffb5db5b4911 completed March 1, 2026, 10:23 p.m.
PD Predicate disambiguation batch_69a4bb4d4104819084027a043c6118cb completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:44 p.m.