Triple

T26905853
Position Surface form Disambiguated ID Type / Status
Subject district council of Berendrecht-Zandvliet-Lillo E677250 entity
Predicate governs P760 FINISHED
Object Zandvliet
Zandvliet is a village in the northern part of Antwerp, Belgium, known for its historic fortifications and location near the Port of Antwerp.
E2293431 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: Zandvliet | Statement: [district council of Berendrecht-Zandvliet-Lillo, governs, Zandvliet]
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: Zandvliet
Triple: [district council of Berendrecht-Zandvliet-Lillo, governs, Zandvliet]
Generated description
Zandvliet is a village in the northern part of Antwerp, Belgium, known for its historic fortifications and location near the Port of Antwerp.

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_69eee9bcef1c8190be88586bb902bb9b completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fb2e9808190a27e6fb40a310d9d completed May 2, 2026, 4 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7aa8cbab088190b62d060779606fcf completed Aug. 11, 2026, 4:44 a.m.
NEDg Description generation batch_6a7aa97357408190a09d63683851f5da completed Aug. 11, 2026, 4:47 a.m.
NED2 Entity disambiguation (via description) batch_6a7aa9fbae7881908349dd1f226e05d7 completed Aug. 11, 2026, 4:50 a.m.
Created at: April 27, 2026, 5:59 a.m.