Triple

T26602119
Position Surface form Disambiguated ID Type / Status
Subject Kachari Kingdom E667662 entity
Predicate notableSite P2462 FINISHED
Object Dimapur ruins
Dimapur ruins are the archaeological remains of an ancient Kachari capital in Nagaland, India, known for their megalithic structures and richly carved stone monuments.
E1731344 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: Dimapur ruins | Statement: [Kachari Kingdom, notableSite, Dimapur ruins]
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: Dimapur ruins
Triple: [Kachari Kingdom, notableSite, Dimapur ruins]
Generated description
Dimapur ruins are the archaeological remains of an ancient Kachari capital in Nagaland, India, known for their megalithic structures and richly carved stone monuments.

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_69ee9cfd20348190bb1255d2603efb7a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f61570d4e08190bbe6f89efc3b9b54 completed May 2, 2026, 3:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c8415e048190a6e94d953734c0eb completed May 23, 2026, 3:31 p.m.
NEDg Description generation batch_6a11c8f290bc8190bfa1990ee7119516 completed May 23, 2026, 3:34 p.m.
NED2 Entity disambiguation (via description) batch_6a11ca5af2a88190b64f3929d0abb7c8 completed May 23, 2026, 3:40 p.m.
Created at: April 27, 2026, 2:12 a.m.