Triple

T34636418
Position Surface form Disambiguated ID Type / Status
Subject Peperbus tower E889438 entity
Predicate locatedNear P294 FINISHED
Object Grote Kerkplein, Zwolle
Grote Kerkplein in Zwolle is a central historic square known for its proximity to the iconic Peperbus tower and its role as a cultural and social gathering place in the city.
E2105088 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: Grote Kerkplein, Zwolle | Statement: [Peperbus tower, locatedNear, Grote Kerkplein, Zwolle]
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: Grote Kerkplein, Zwolle
Triple: [Peperbus tower, locatedNear, Grote Kerkplein, Zwolle]
Generated description
Grote Kerkplein in Zwolle is a central historic square known for its proximity to the iconic Peperbus tower and its role as a cultural and social gathering place in the city.

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_69f349d724848190b63ad3407e0006d9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7226c1f9c8190aa1536777e45e8ef completed May 3, 2026, 10:24 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3748ec67488190999701b7a18cbd34 completed June 21, 2026, 2:14 a.m.
NEDg Description generation batch_6a37496746188190bf52190a4dbb0f2e completed June 21, 2026, 2:16 a.m.
NED2 Entity disambiguation (via description) batch_6a3749ec99a881909ebe245b31d13079 completed June 21, 2026, 2:18 a.m.
Created at: May 1, 2026, 2:04 a.m.