Triple

T3408125
Position Surface form Disambiguated ID Type / Status
Subject Liaoning E71823 entity
Predicate hasMajorPort P942 FINISHED
Object Dandong Port E301373 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: Dandong Port | Statement: [Liaoning, hasMajorPort, Dandong Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dandong Port
Context triple: [Liaoning, hasMajorPort, Dandong Port]
  • A. Yingkou Port
    Yingkou Port is a major seaport in northeastern China that serves as a key maritime gateway for Liaoning Province and the broader Northeast Asia region.
  • B. Port of Dalian
    The Port of Dalian is a major deep-water seaport in northeastern China that serves as a key gateway for international trade and shipping in the Bohai Sea region.
  • C. Dandong chosen
    Dandong is a northeastern Chinese border city on the Yalu River, known as a key gateway for trade and transport between China and North Korea.
  • D. Yantai Port
    Yantai Port is a major seaport city and shipping hub on the Bohai Sea coast in northeastern Shandong Province, China.
  • E. Huangshi Port
    Huangshi Port is a river port facility serving the city of Huangshi in Hubei Province, China, supporting regional cargo transport and trade along the Yangtze River.
  • 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_69ad85ac312481909e7027ced1456a9f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb9056acc8190a9c50ec374851ac8 completed March 8, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360be3b6c81909ee0ac6d4512a56d completed March 13, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:15 p.m.