Triple

T34895551
Position Surface form Disambiguated ID Type / Status
Subject Tabatinga E1006421 entity
Predicate locatedNear P294 FINISHED
Object Leticia Airport
Leticia Airport is a regional airport serving the border city of Leticia in Colombia’s Amazon region, providing vital air connectivity to this remote tri-border area with Brazil and Peru.
E2141394 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: Leticia Airport | Statement: [Tabatinga, locatedNear, Leticia Airport]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Leticia Airport
Triple: [Tabatinga, locatedNear, Leticia Airport]
Generated description
Leticia Airport is a regional airport serving the border city of Leticia in Colombia’s Amazon region, providing vital air connectivity to this remote tri-border area with Brazil and Peru.

Provenance (5 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_69f76dbfe5788190ad8b64f241f470c8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f781c22ec081908d6ddf8fd9436c35 completed May 3, 2026, 5:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a383696bb7081908d7450dd4df29b19 completed June 21, 2026, 7:08 p.m.
NEDg Description generation batch_6a3839b55b588190aff0eed4f777127a completed June 21, 2026, 7:21 p.m.
NED2 Entity disambiguation (via description) batch_6a383a1845208190b74d541babe41b95 completed June 21, 2026, 7:23 p.m.
Created at: May 3, 2026, 4 p.m.