Triple

T24137888
Position Surface form Disambiguated ID Type / Status
Subject Mao Naga E598138 entity
Predicate associatedDistrict P29284 FINISHED
Object Senapati district
Senapati district is an administrative district in the northeastern Indian state of Manipur, known for its hilly terrain and diverse indigenous communities.
E1736576 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: Senapati district | Statement: [Mao Naga, associatedDistrict, Senapati district]
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: Senapati district
Triple: [Mao Naga, associatedDistrict, Senapati district]
Generated description
Senapati district is an administrative district in the northeastern Indian state of Manipur, known for its hilly terrain and diverse indigenous communities.

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_69e288c92e448190ac57034fa0c863ce completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1df7e3c20819099ff289789829d7e completed April 29, 2026, 10:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe3c74f0819099fd30db204d4b1c completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11fec26524819083f733b7471946c3 completed May 23, 2026, 7:23 p.m.
NED2 Entity disambiguation (via description) batch_6a11ff33e3448190996da2faf6f3f6b5 completed May 23, 2026, 7:25 p.m.
Created at: April 17, 2026, 11:27 p.m.