Triple

T22339878
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Central Station ferry terminal E552244 entity
Predicate operatedBy P86 FINISHED
Object GVB 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: GVB | Statement: [Amsterdam Central Station ferry terminal, operatedBy, GVB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GVB
Context triple: [Amsterdam Central Station ferry terminal, operatedBy, GVB]
  • A. GVB chosen
    GVB is Amsterdam’s primary public transport company, operating the city’s trams, buses, metro, and ferries.
  • B. GVB zone 5700
    GVB zone 5700 is a public transport fare zone in Amsterdam’s central area that includes Nieuwmarkt metro station.
  • C. GVB Amsterdam
    GVB Amsterdam is the primary public transport operator in Amsterdam, running the city’s trams, buses, metros, and ferries.
  • D. GVB bus network
    The GVB bus network is Amsterdam’s municipal bus system, providing extensive urban and regional public transport connections throughout the city and surrounding areas.
  • E. GVB zone 5711
    GVB zone 5711 is a public transport fare zone in Amsterdam that includes Bullewijk metro station within the GVB ticketing system.
  • 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_69e11e494eec81909c4d2d51f69499d9 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157824f588190882bea9e61dd5a83 completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:43 p.m.