Triple

T27770873
Position Surface form Disambiguated ID Type / Status
Subject Drongen railway station E701739 entity
Predicate hasAddressLocality P7943 FINISHED
Object Drongen district
Drongen district is a suburban area of the city of Ghent in Belgium, known for its residential character and proximity to the Drongen railway station.
E1790041 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: Drongen district | Statement: [Drongen railway station, hasAddressLocality, Drongen district]
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: Drongen district
Triple: [Drongen railway station, hasAddressLocality, Drongen district]
Generated description
Drongen district is a suburban area of the city of Ghent in Belgium, known for its residential character and proximity to the Drongen railway station.

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_69ef6a52fa708190934a32308d2c92dc completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63796dd688190a72de4e61faaac9b completed May 2, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ecbb00388190b3d2cc7a2efd1cdf completed May 24, 2026, 12:19 p.m.
NEDg Description generation batch_6a12ed49266881909fd55a7028ad6a1f completed May 24, 2026, 12:21 p.m.
NED2 Entity disambiguation (via description) batch_6a12ee215b4c8190aeef56575c0c0015 completed May 24, 2026, 12:25 p.m.
Created at: April 27, 2026, 4:35 p.m.