Triple

T3230296
Position Surface form Disambiguated ID Type / Status
Subject Trincomalee Airport E67721 entity
Predicate serves P98 FINISHED
Object Trincomalee E12376 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: Trincomalee | Statement: [Trincomalee Airport, serves, Trincomalee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trincomalee
Context triple: [Trincomalee Airport, serves, Trincomalee]
  • A. Trincomalee chosen
    Trincomalee is a strategically important natural deep-water harbor and coastal city on the northeastern coast of Sri Lanka.
  • B. Hambantota
    Hambantota is a coastal city in southern Sri Lanka known for its rapid development, including major infrastructure projects like a deep-sea port and international airport.
  • C. Hikkaduwa
    Hikkaduwa is a coastal town in southern Sri Lanka known for its beaches, coral reefs, and surf culture.
  • D. Batticaloa
    Batticaloa is a coastal city in eastern Sri Lanka known historically as an important regional port and trading center.
  • E. Koggala
    Koggala is a coastal town in southern Sri Lanka known for its scenic beach, lagoon, and proximity to the historic city of Galle.
  • 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_69ad858c61888190a31196310d9b30b5 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaeb99e088190a8eeca2ca53707e7 completed March 8, 2026, 5:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb6ae0bc8190a64ab7c2a842495b completed March 13, 2026, 7:23 a.m.
Created at: March 8, 2026, 3:08 p.m.