Triple

T25933846
Position Surface form Disambiguated ID Type / Status
Subject Sanjak of Novi Pazar E653499 entity
Predicate borderedBy P224 FINISHED
Object Sanjak of Sjenica
The Sanjak of Sjenica was an Ottoman administrative district in the western Balkans centered on the town of Sjenica, in what is now southwestern Serbia.
E1726887 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: Sanjak of Sjenica | Statement: [Sanjak of Novi Pazar, borderedBy, Sanjak of Sjenica]
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: Sanjak of Sjenica
Triple: [Sanjak of Novi Pazar, borderedBy, Sanjak of Sjenica]
Generated description
The Sanjak of Sjenica was an Ottoman administrative district in the western Balkans centered on the town of Sjenica, in what is now southwestern Serbia.

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_69e7ab3eb9b881909c1390690551f868 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6041afd808190a105a5d8b798e64b completed May 2, 2026, 2:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11baf52c84819099eee702539e1de3 completed May 23, 2026, 2:34 p.m.
NEDg Description generation batch_6a11bb97c4208190aae3433b12358750 completed May 23, 2026, 2:37 p.m.
NED2 Entity disambiguation (via description) batch_6a11be83120c819096ca5fc2f18a4739 completed May 23, 2026, 2:49 p.m.
Created at: April 22, 2026, 8:37 a.m.