Triple

T12946933
Position Surface form Disambiguated ID Type / Status
Subject Kyaukphyu E309793 entity
Predicate hasPort P35 FINISHED
Object Kyaukphyu Port E309793 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: Kyaukphyu Port | Statement: [Kyaukphyu, hasPort, Kyaukphyu Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kyaukphyu Port
Context triple: [Kyaukphyu, hasPort, Kyaukphyu Port]
  • A. Mongla Port
    Mongla Port is Bangladesh’s second-largest seaport, serving as a key maritime gateway in the country’s southwest region.
  • B. Kyaukphyu chosen
    Kyaukphyu is a coastal town in western Myanmar that serves as a strategic deep-water port and hub for regional trade and energy projects.
  • C. Kalabahi Port
    Kalabahi Port is the main seaport and maritime gateway serving the island and regency of Alor in East Nusa Tenggara, Indonesia.
  • D. Port of Yangon
    The Port of Yangon is Myanmar’s principal seaport and trade gateway, handling the majority of the country’s maritime cargo and connecting it to regional and global shipping routes.
  • E. Cua Lo Port
    Cua Lo Port is a coastal seaport in north-central Vietnam that serves as a key maritime gateway for Nghe An Province and the surrounding region.
  • 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_69d7bdfb57a88190836b743e2825feca completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97e1c67b8819094e5243267f93ce2 completed April 10, 2026, 10:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8d9669c819090471eb7e035d83d completed May 3, 2026, 2:54 a.m.
Created at: April 9, 2026, 5:43 p.m.