Triple

T14524337
Position Surface form Disambiguated ID Type / Status
Subject TRR E340732 entity
Predicate airportServes P4363 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: [TRR, airportServes, Trincomalee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trincomalee
Context triple: [TRR, airportServes, 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. Puttalam
    Puttalam is a coastal town in northwestern Sri Lanka known for its salt industry, lagoon fisheries, and proximity to major wind farms.
  • D. Pallamallawa
    Pallamallawa is a small rural village in northern New South Wales, Australia, known for its agricultural surroundings and close-knit community.
  • E. Seethawaka
    Seethawaka is a historically significant town and administrative area in Sri Lanka’s Western Province, known for its role in the 16th-century Seethawaka kingdom and its lush, hilly landscape.
  • 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_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dea04f16f88190ba357b0f8021b46b completed April 14, 2026, 8:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdd5c1bf988190b1265c3db9a6b590 completed May 8, 2026, 12:23 p.m.
Created at: April 10, 2026, 1:22 a.m.