Triple

T23072137
Position Surface form Disambiguated ID Type / Status
Subject Rotterdam road network E575224 entity
Predicate includes P1393 FINISHED
Object Maastunnel 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: Maastunnel | Statement: [Rotterdam road network, includes, Maastunnel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maastunnel
Context triple: [Rotterdam road network, includes, Maastunnel]
  • A. Maastunnel chosen
    Maastunnel is a historic traffic tunnel in Rotterdam, the Netherlands, carrying road, bicycle, and pedestrian traffic beneath the Nieuwe Maas river.
  • B. Oslo Tunnel
    The Oslo Tunnel is a central railway tunnel in Oslo, Norway, that carries most of the city's mainline train traffic between its principal stations.
  • C. Eiksund Tunnel
    The Eiksund Tunnel is a deep undersea road tunnel in western Norway that links islands in Møre og Romsdal county to the mainland as part of the regional highway network.
  • D. Hvaler Tunnel
    Hvaler Tunnel is an undersea road tunnel in Norway that connects the Hvaler archipelago to the mainland.
  • E. Muskö Tunnel
    Muskö Tunnel is a Swedish underwater road tunnel connecting the island of Muskö to the mainland, notable for serving the strategic Muskö naval base.
  • 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_69e245be28d48190ad1348d5a73db37d completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18c5ffad881909ed626045c15dd33 completed April 29, 2026, 4:43 a.m.
Created at: April 17, 2026, 3:56 p.m.