Triple

T26198676
Position Surface form Disambiguated ID Type / Status
Subject Ahom–Mughal conflicts E655173 entity
Predicate hasPart P35 FINISHED
Object Battle of Samdhara
The Battle of Samdhara was a significant military engagement between the Ahom kingdom and the Mughal Empire during their protracted conflicts in northeastern India.
E1721095 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: Battle of Samdhara | Statement: [Ahom–Mughal conflicts, hasPart, Battle of Samdhara]
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: Battle of Samdhara
Triple: [Ahom–Mughal conflicts, hasPart, Battle of Samdhara]
Generated description
The Battle of Samdhara was a significant military engagement between the Ahom kingdom and the Mughal Empire during their protracted conflicts in northeastern India.

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_69ee5b48236c81908fe385b6afc4f60b completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60cd8c4608190bdf0cc6142264239 completed May 2, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a119a434ad8819093ad0069180080a4 completed May 23, 2026, 12:14 p.m.
NEDg Description generation batch_6a119b1444008190a4cdcbe5fd8bca98 completed May 23, 2026, 12:18 p.m.
NED2 Entity disambiguation (via description) batch_6a119c2d13388190869495b5b068ab15 completed May 23, 2026, 12:23 p.m.
Created at: April 26, 2026, 8:47 p.m.