Triple

T28689866
Position Surface form Disambiguated ID Type / Status
Subject Stefan Dragutin E729246 entity
Predicate heldTitle P8 FINISHED
Object Lord of Mačva
Lord of Mačva was a medieval noble title associated with the Mačva region, historically held by Serbian and Hungarian rulers as a significant frontier lordship in the Balkans.
E1828205 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: Lord of Mačva | Statement: [Stefan Dragutin, heldTitle, Lord of Mačva]
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: Lord of Mačva
Triple: [Stefan Dragutin, heldTitle, Lord of Mačva]
Generated description
Lord of Mačva was a medieval noble title associated with the Mačva region, historically held by Serbian and Hungarian rulers as a significant frontier lordship in the Balkans.

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_69f043e60b6c8190ac2cd042e77fe6e9 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65684223c8190867c123acf504527 completed May 2, 2026, 7:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cc3b0436481909b6a4c9e4dfc9cfa completed May 31, 2026, 11:26 p.m.
NEDg Description generation batch_6a1cc46491208190b29352509e2dbc79 completed May 31, 2026, 11:29 p.m.
NED2 Entity disambiguation (via description) batch_6a1cc4ff58dc8190a81f7ad27e6b6fa8 completed May 31, 2026, 11:32 p.m.
Created at: April 28, 2026, 5:35 a.m.