Triple

T20262761
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam North–South line E498885 entity
Predicate hasStation P35 FINISHED
Object Rokin metro station 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: Rokin metro station | Statement: [Amsterdam North–South line, hasStation, Rokin metro station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rokin metro station
Context triple: [Amsterdam North–South line, hasStation, Rokin metro station]
  • A. Rokin metro station chosen
    Rokin metro station is an underground station on Amsterdam’s North–South metro line, located beneath the Rokin street in the city center.
  • B. Rhoon metro station
    Rhoon metro station is a rapid transit station on the Rotterdam Metro network serving the village of Rhoon in the Netherlands.
  • C. Shoush Metro Station
    Shoush Metro Station is a stop on Tehran’s Metro system serving passengers along Line 1 in the Shoush neighborhood.
  • D. Gein metro station
    Gein metro station is a southern terminus of the Amsterdam Metro network, serving the Gein neighborhood in the borough of Amsterdam-Zuidoost.
  • E. Nyamiha metro station
    Nyamiha metro station is a Minsk Metro station named after and located near the historic Nyamiha River in central Minsk, Belarus.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674cba2748190a886ecd8316dc518 completed April 20, 2026, 6:47 p.m.
Created at: April 11, 2026, 11:41 p.m.