Triple

T22586506
Position Surface form Disambiguated ID Type / Status
Subject Transportation in Pierce County, Washington E564808 entity
Predicate seaportFunction P17285 FINISHED
Object container shipping 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: container shipping | Statement: [Transportation in Pierce County, Washington, seaportFunction, container shipping]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seaportFunction
Context triple: [Transportation in Pierce County, Washington, seaportFunction, container shipping]
  • A. portFunction chosen
    Indicates the specific operational role or purpose that a port serves within a system or network.
  • B. shipFunction
    Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
  • C. hasSeaportStatus
    Indicates that an entity possesses the status or designation of being a seaport or having seaport facilities.
  • D. supplyPort
    Indicates that one entity serves as a source or interface through which resources, materials, or energy are provided to another entity.
  • E. maritimeFunction
    Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
  • 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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1615d1fe081908079f777cdab12a2 completed April 29, 2026, 1:39 a.m.
PD Predicate disambiguation batch_69ee626e6bb08190ada4dd8b48cc0c43 completed April 26, 2026, 7:07 p.m.
Created at: April 17, 2026, 2:46 p.m.