Triple

T25397340
Position Surface form Disambiguated ID Type / Status
Subject Torsa River E636326 entity
Predicate crossesBorderBetween P4105 FINISHED
Object Bhutan and India
Bhutan and India are neighboring South Asian countries that share close political, economic, and cultural ties, including several transboundary rivers and an open border.
E15914 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: Bhutan and India | Statement: [Torsa River, crossesBorderBetween, Bhutan and India]
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: Bhutan and India
Triple: [Torsa River, crossesBorderBetween, Bhutan and India]
Generated description
Bhutan and India are neighboring South Asian countries that share close political, economic, and cultural ties, including several transboundary rivers and an open border.

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_69e75db263888190b77fff9e2827b9a2 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f584f5dda88190a24d7fb4ab0a45bd completed May 2, 2026, 5 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10b72fe2548190beba9b8c87581c9a completed May 22, 2026, 8:06 p.m.
NEDg Description generation batch_6a10b94377108190a5fb35e99b5f0351 completed May 22, 2026, 8:14 p.m.
NED2 Entity disambiguation (via description) batch_6a10b9c6dbf48190abe4efb4035db2a0 completed May 22, 2026, 8:17 p.m.
Created at: April 21, 2026, 1:50 p.m.