Triple

T15660270
Position Surface form Disambiguated ID Type / Status
Subject Jilong E376548 entity
Predicate knownFor P22 FINISHED
Object Keelung Harbor 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: Keelung Harbor | Statement: [Jilong, knownFor, Keelung Harbor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keelung Harbor
Context triple: [Jilong, knownFor, Keelung Harbor]
  • A. 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.
  • B. 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.
  • C. Keelung chosen
    Keelung is a major port city in northeastern Taiwan known for its busy harbor, seafood markets, and coastal scenery.
  • D. Magong Harbor
    Magong Harbor is a key maritime port and transportation hub in Magong City on Taiwan’s Penghu Islands, serving both commercial shipping and passenger ferries.
  • E. Donggang Port
    Donggang Port is a major fishing and transportation harbor in southern Taiwan known for its seafood markets and access to nearby offshore islands.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ef4e6a08190ad8bbafaa3612f22 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff82e921e48190b5b5f4006ad65844 completed May 9, 2026, 6:54 p.m.
Created at: April 10, 2026, 4:15 a.m.