Triple

T26939550
Position Surface form Disambiguated ID Type / Status
Subject Municipality of Cerklje na Gorenjskem E678473 entity
Predicate hasSettlement P1068 FINISHED
Object Zgornji Brnik
Zgornji Brnik is a village in northern Slovenia located near Ljubljana Jože Pučnik Airport within the Municipality of Cerklje na Gorenjskem.
E1785245 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: Zgornji Brnik | Statement: [Municipality of Cerklje na Gorenjskem, hasSettlement, Zgornji Brnik]
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: Zgornji Brnik
Triple: [Municipality of Cerklje na Gorenjskem, hasSettlement, Zgornji Brnik]
Generated description
Zgornji Brnik is a village in northern Slovenia located near Ljubljana Jože Pučnik Airport within the Municipality of Cerklje na Gorenjskem.

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_69eeeb4d69588190a7c912164a1c37b3 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f62051d4388190a043bae51a734e8d completed May 2, 2026, 4:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12e42f749c8190828b02fa6eba7229 completed May 24, 2026, 11:42 a.m.
NEDg Description generation batch_6a12e4da65dc8190801cafed5fb95685 completed May 24, 2026, 11:45 a.m.
NED2 Entity disambiguation (via description) batch_6a12e5acc5c8819081be9900ea407d65 completed May 24, 2026, 11:49 a.m.
Created at: April 27, 2026, 6:17 a.m.