Triple

T25846606
Position Surface form Disambiguated ID Type / Status
Subject Kamrup district E651085 entity
Predicate borderedBy P224 FINISHED
Object Rangia subdivision
Rangia subdivision is an administrative subdivision in Assam, India, known for encompassing the town of Rangia and surrounding rural areas within the Kamrup region.
E1698622 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: Rangia subdivision | Statement: [Kamrup district, borderedBy, Rangia subdivision]
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: Rangia subdivision
Triple: [Kamrup district, borderedBy, Rangia subdivision]
Generated description
Rangia subdivision is an administrative subdivision in Assam, India, known for encompassing the town of Rangia and surrounding rural areas within the Kamrup region.

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_69e7ab38086081908f3a8e7e0c6efd83 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6023837c481908c17d2e7f89aeed6 completed May 2, 2026, 1:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10da349c648190873f6adb3801aacb completed May 22, 2026, 10:35 p.m.
NEDg Description generation batch_6a10dbe1a77481908aa6318c168959fa completed May 22, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a10dc7a3a50819089ed854ac6463fe6 completed May 22, 2026, 10:45 p.m.
Created at: April 22, 2026, 7:53 a.m.