Triple

T28441250
Position Surface form Disambiguated ID Type / Status
Subject Hammadid dynasty E715715 entity
Predicate notableRuler P22 FINISHED
Object al-Mansur ibn Nasir
Al-Mansur ibn Nasir was a medieval Berber ruler who led the Hammadid dynasty in North Africa during its period of regional power and cultural flourishing.
E1821807 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: al-Mansur ibn Nasir | Statement: [Hammadid dynasty, notableRuler, al-Mansur ibn Nasir]
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: al-Mansur ibn Nasir
Triple: [Hammadid dynasty, notableRuler, al-Mansur ibn Nasir]
Generated description
Al-Mansur ibn Nasir was a medieval Berber ruler who led the Hammadid dynasty in North Africa during its period of regional power and cultural flourishing.

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_69efd6b44550819094ae991b553d9fc3 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e3da3908190a38f80a9fe4cadba completed May 2, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cac3b2044819098b3e4a58117418e completed May 31, 2026, 9:46 p.m.
NEDg Description generation batch_6a1cacfc26bc8190ad65e3f8ef7d6d7b completed May 31, 2026, 9:49 p.m.
NED2 Entity disambiguation (via description) batch_6a1cadf50e1c81908235678a32385afb completed May 31, 2026, 9:53 p.m.
Created at: April 28, 2026, 1:46 a.m.