Triple

T30096031
Position Surface form Disambiguated ID Type / Status
Subject Braničevo District E764865 entity
Predicate hasCulturalSite P1098 FINISHED
Object Tumane Monastery
Tumane Monastery is a Serbian Orthodox monastery in eastern Serbia, known as a significant spiritual and pilgrimage center with a long monastic tradition.
E1902270 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: Tumane Monastery | Statement: [Braničevo District, hasCulturalSite, Tumane Monastery]
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: Tumane Monastery
Triple: [Braničevo District, hasCulturalSite, Tumane Monastery]
Generated description
Tumane Monastery is a Serbian Orthodox monastery in eastern Serbia, known as a significant spiritual and pilgrimage center with a long monastic tradition.

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_69f22474e4288190b5f895fe3974aa92 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67d90de4881909fa48ca060068046 completed May 2, 2026, 10:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a274ca21d208190b0f4c9e6efd01b49 completed June 8, 2026, 11:13 p.m.
NEDg Description generation batch_6a274e10e14481909da1d624fd8c1084 completed June 8, 2026, 11:19 p.m.
NED2 Entity disambiguation (via description) batch_6a274ef7cbb081909ec7a761b8873bc7 completed June 8, 2026, 11:23 p.m.
Created at: April 29, 2026, 7:07 p.m.