Triple

T21669033
Position Surface form Disambiguated ID Type / Status
Subject TEC E534795 entity
Predicate collaboratesWith P37 FINISHED
Object De Lijn NE NERFINISHED

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: De Lijn | Statement: [TEC, collaboratesWith, De Lijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: De Lijn
Context triple: [TEC, collaboratesWith, De Lijn]
  • A. De Lijn chosen
    De Lijn is the Flemish public transport company in Belgium that operates most regional bus and tram services in Flanders.
  • B. De Lijn tram network
    The De Lijn tram network is a regional public transport system in Flanders, Belgium, operating urban and interurban tram services that complement and connect with De Lijn’s bus network.
  • C. Oude Lijn
    The Oude Lijn is the oldest railway line in the Netherlands, connecting key cities such as Amsterdam, Haarlem, Leiden, The Hague, and Rotterdam.
  • D. Hoekse Lijn
    Hoekse Lijn is a railway line in the Netherlands that connects Rotterdam with the coastal town of Hoek van Holland.
  • E. De Lijn bus lines
    De Lijn bus lines are regional public bus services operated by the Flemish transport company De Lijn, connecting cities and towns throughout Flanders and parts of Brussels.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46898008190aa618a4af55bd1ee completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c0e008c8190a549d275b1c98e0b completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:37 p.m.