Triple

T15476639
Position Surface form Disambiguated ID Type / Status
Subject Hsinchu–Taipei–Keelung corridor E376795 entity
Predicate hasPort P35 FINISHED
Object Port of Keelung E77406 NE 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: Port of Keelung | Statement: [Hsinchu–Taipei–Keelung corridor, hasPort, Port of Keelung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Keelung
Context triple: [Hsinchu–Taipei–Keelung corridor, hasPort, Port of Keelung]
  • A. Port of Taipei
    The Port of Taipei is a major international seaport in northern Taiwan that serves as a key hub for container shipping and maritime trade.
  • B. Port of Kaohsiung
    The Port of Kaohsiung is Taiwan’s largest and busiest seaport, serving as a major international hub for container shipping and maritime trade in East Asia.
  • C. Keelung chosen
    Keelung is a major port city in northeastern Taiwan known for its busy harbor, seafood markets, and coastal scenery.
  • D. Hualien Port
    Hualien Port is a major commercial and tourist seaport on Taiwan’s eastern coast, serving as a key hub for maritime trade and cruise travel in the region.
  • E. Keelung Station
    Keelung Station is a major railway terminus in northern Taiwan serving the port city of Keelung on the Taiwan Railways network.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f88a5dc8190a2d7830748e29180 completed April 16, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2d093ccc8190aefc355a837c83f4 completed May 9, 2026, 12:48 p.m.
Created at: April 10, 2026, 3:34 a.m.