Triple

T29036076
Position Surface form Disambiguated ID Type / Status
Subject Fruška Gora National Park E737861 entity
Predicate contains P35 FINISHED
Object Velika Remeta Monastery
Velika Remeta Monastery is a Serbian Orthodox monastery on Fruška Gora, renowned for its medieval origins and traditional monastic architecture.
E1853741 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: Velika Remeta Monastery | Statement: [Fruška Gora National Park, contains, Velika Remeta 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: Velika Remeta Monastery
Triple: [Fruška Gora National Park, contains, Velika Remeta Monastery]
Generated description
Velika Remeta Monastery is a Serbian Orthodox monastery on Fruška Gora, renowned for its medieval origins and traditional monastic architecture.

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_69f077efb3848190b41574e1670f6ae2 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f6603c9e4081908129011e8294db5a completed May 2, 2026, 8:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25504594548190ad8b9653d5b1ff56 completed June 7, 2026, 11:04 a.m.
NEDg Description generation batch_6a25547c1cb881909b0a85b2bb6d61f1 completed June 7, 2026, 11:22 a.m.
NED2 Entity disambiguation (via description) batch_6a2558d511dc81909587cbd426bda0b6 completed June 7, 2026, 11:41 a.m.
Created at: April 28, 2026, 9:58 a.m.