Triple

T38501251
Position Surface form Disambiguated ID Type / Status
Subject Porte de Hal metro station E919840 entity
Predicate servedByLine P1293 FINISHED
Object Brussels Metro line 2
Brussels Metro line 2 is a circular rapid transit line in Brussels, Belgium, forming part of the city’s core metro network and serving numerous central and inner-ring stations.
E55760 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: Brussels Metro line 2 | Statement: [Porte de Hal metro station, servedByLine, Brussels Metro line 2]
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: Brussels Metro line 2
Triple: [Porte de Hal metro station, servedByLine, Brussels Metro line 2]
Generated description
Brussels Metro line 2 is a circular rapid transit line in Brussels, Belgium, forming part of the city’s core metro network and serving numerous central and inner-ring stations.

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_69f76e9ddd4481908f8c04439d848f9d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd26356188190b8c94a1a78071c30 completed May 7, 2026, 5:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41f42f352c819094ef892cc0e1a746 completed June 29, 2026, 4:27 a.m.
NEDg Description generation batch_6a41f4d0afe4819093c6b93163cddfe5 completed June 29, 2026, 4:30 a.m.
NED2 Entity disambiguation (via description) batch_6a41f54e7d6c81909bac42ff59a0e27e completed June 29, 2026, 4:32 a.m.
Created at: May 3, 2026, 4:31 p.m.