Triple

T35152430
Position Surface form Disambiguated ID Type / Status
Subject Waasland E1015028 entity
Predicate hasRailConnection P848 FINISHED
Object Ghent–Antwerp railway line
The Ghent–Antwerp railway line is a major Belgian rail route linking the historic city of Ghent with the port city of Antwerp and serving the surrounding Waasland region.
E2126774 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: Ghent–Antwerp railway line | Statement: [Waasland, hasRailConnection, Ghent–Antwerp railway line]
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: Ghent–Antwerp railway line
Triple: [Waasland, hasRailConnection, Ghent–Antwerp railway line]
Generated description
The Ghent–Antwerp railway line is a major Belgian rail route linking the historic city of Ghent with the port city of Antwerp and serving the surrounding Waasland region.

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_69f76ddb3a708190b521ba2970b17178 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78cefb12c8190a955da746e14799f completed May 3, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37d96241508190ab7303b610002646 completed June 21, 2026, 12:30 p.m.
NEDg Description generation batch_6a37da795c248190b902371c68f5d60c completed June 21, 2026, 12:35 p.m.
NED2 Entity disambiguation (via description) batch_6a37daf5baa88190883fdd8eab7fc501 completed June 21, 2026, 12:37 p.m.
Created at: May 3, 2026, 4:02 p.m.