Triple

T23436931
Position Surface form Disambiguated ID Type / Status
Subject Feni District E563488 entity
Predicate hasUpazila P68838 FINISHED
Object Daganbhuiyan Upazila
Daganbhuiyan Upazila is an administrative sub-district in southeastern Bangladesh, known for its predominantly rural communities and agriculture-based local economy.
E581626 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: Daganbhuiyan Upazila | Statement: [Feni District, hasUpazila, Daganbhuiyan Upazila]
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: Daganbhuiyan Upazila
Triple: [Feni District, hasUpazila, Daganbhuiyan Upazila]
Generated description
Daganbhuiyan Upazila is an administrative sub-district in southeastern Bangladesh, known for its predominantly rural communities and agriculture-based local economy.

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_69e24553980c8190bb66a2ae0bdab125 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a5dcd4608190a543cc747e0daab8 completed April 29, 2026, 6:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbcdce6c88190851e8b25cb85a6fe completed May 22, 2026, 2:18 a.m.
NEDg Description generation batch_6a0fbdf3fc5c8190b8dc7e5c2416b02b completed May 22, 2026, 2:22 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbe7e12188190803c1954112de4e6 completed May 22, 2026, 2:25 a.m.
Created at: April 17, 2026, 5:50 p.m.