Triple

T20275354
Position Surface form Disambiguated ID Type / Status
Subject Port of Corinto E502999 entity
Predicate locatedIn P40 FINISHED
Object Corinto E503000 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: Corinto | Statement: [Port of Corinto, locatedIn, Corinto]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corinto
Context triple: [Port of Corinto, locatedIn, Corinto]
  • A. Corinto chosen
    Corinto is a major Pacific seaport town in northwestern Nicaragua that serves as one of the country’s principal maritime gateways for trade.
  • B. Corinto
    Corinto is a municipality located in the Morazán Department of northeastern El Salvador, known for its rural character and mountainous landscapes.
  • C. Corinth
    Corinth is a small unincorporated community located in Coweta County, Georgia, United States.
  • D. Corinth
    Corinth was an influential ancient Greek city-state strategically located on the Isthmus of Corinth, known for its wealth, maritime trade, and cultural significance.
  • E. Corinth
    Corinth is a small town and village in Saratoga County, New York, known for its historic paper mills and location along the Hudson River near the Adirondack foothills.
  • 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_69e0b4b0e79c8190bd61f22ef1329fa8 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e675e30d4c8190a9e2d9efa0f741fc completed April 20, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a085a21233881908fb835541ae88c70 completed May 16, 2026, 11:50 a.m.
Created at: April 16, 2026, 10:32 a.m.