Triple

T12653434
Position Surface form Disambiguated ID Type / Status
Subject former Maliebaan railway station E302221 entity
Predicate locatedOn P40 FINISHED
Object Maliebaan E996614 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: Maliebaan | Statement: [former Maliebaan railway station, locatedOn, Maliebaan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maliebaan
Context triple: [former Maliebaan railway station, locatedOn, Maliebaan]
  • A. Maliebaan chosen
    Maliebaan is a historic tree-lined avenue in Utrecht, Netherlands, known for its 17th-century origins as a sporting lane and its later cultural and political significance.
  • B. Heemraadlaan
    Heemraadlaan is a metro station in Spijkenisse, Netherlands, serving as part of the Rotterdam Metro network.
  • C. Mahlaing
    Mahlaing is a town located in central Myanmar’s Mandalay Region.
  • D. Klaaswaal
    Klaaswaal is a village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • E. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96160730c81909e1aa3efb51bf159 completed April 10, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6719c18508190a9c28b2526e6b336 completed May 2, 2026, 9:50 p.m.
Created at: April 9, 2026, 5:18 p.m.