Triple

T25570203
Position Surface form Disambiguated ID Type / Status
Subject Gheg region E640951 entity
Predicate hasSubgroup P747 FINISHED
Object Mirdita region
The Mirdita region is a historically significant, traditionally Catholic highland area in northern Albania known for its strong clan structures and distinct Gheg Albanian culture.
E1699752 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: Mirdita region | Statement: [Gheg region, hasSubgroup, Mirdita region]
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: Mirdita region
Triple: [Gheg region, hasSubgroup, Mirdita region]
Generated description
The Mirdita region is a historically significant, traditionally Catholic highland area in northern Albania known for its strong clan structures and distinct Gheg Albanian culture.

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_69e75dc281bc819095ec04dc0c3a94d0 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8ffb11c8190add0643923c6eaf8 completed May 2, 2026, 1:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ec90161481908b38346714e33e18 completed May 22, 2026, 11:53 p.m.
NEDg Description generation batch_6a10ed7a51a481909346a6926eb90033 completed May 22, 2026, 11:57 p.m.
NED2 Entity disambiguation (via description) batch_6a10ee29be508190865fc3575aff7faa completed May 23, 2026, midnight
Created at: April 21, 2026, 3:57 p.m.