Triple

T20740404
Position Surface form Disambiguated ID Type / Status
Subject Hoekse Lijn (metro line B) E510422 entity
Predicate connects P390 FINISHED
Object Rotterdam 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: Rotterdam | Statement: [Hoekse Lijn (metro line B), connects, Rotterdam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rotterdam
Context triple: [Hoekse Lijn (metro line B), connects, Rotterdam]
  • A. Rotterdam chosen
    Rotterdam is a major Dutch port city known for having one of the world’s largest harbors and striking modern architecture.
  • B. Utrecht
    Utrecht is a small town in South Africa’s KwaZulu-Natal province, known for its scenic surroundings and historical significance dating back to the 19th century.
  • C. Utrecht
    Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
  • D. Dordrecht
    Dordrecht is a historic Dutch city in South Holland known as one of the oldest trading centers in the Netherlands, situated strategically within the Rhine–Meuse–Scheldt river delta.
  • E. Osdorp
    Osdorp is a residential neighborhood in the western part of Amsterdam, Netherlands, known for its post-war urban planning and multicultural population.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20e76ac8190985203b2c17aca14 completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:32 p.m.