Triple

T38212412
Position Surface form Disambiguated ID Type / Status
Subject Mahmud Ahmad E1010584 entity
Predicate militaryBranch P253 FINISHED
Object Mahdist army
The Mahdist army was the religiously motivated military force of the Sudanese Mahdist movement in the late 19th century, known for its role in resisting Egyptian and British control.
 E2260338 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: Mahdist army | Statement: [Mahmud Ahmad, militaryBranch, Mahdist army]
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: Mahdist army
Triple: [Mahmud Ahmad, militaryBranch, Mahdist army]
Generated description
The Mahdist army was the religiously motivated military force of the Sudanese Mahdist movement in the late 19th century, known for its role in resisting Egyptian and British control.

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_69f76dcdc7708190a5f1751d53f40ffe completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcb145d3ac81909b5f69515df4ee9c completed May 7, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a418548be9081909e1f737983642fb4 completed June 28, 2026, 8:34 p.m.
NEDg Description generation batch_6a418629fdd88190869fffe5efa3fe59 completed June 28, 2026, 8:38 p.m.
NED2 Entity disambiguation (via description) batch_6a4186a6b2988190bada9bfa20bc2eee completed June 28, 2026, 8:40 p.m.
Created at: May 3, 2026, 4:30 p.m.