Triple

T22339948
Position Surface form Disambiguated ID Type / Status
Subject Dutch transport infrastructure E552245 entity
Predicate hasHighSpeedRailConnection P48478 FINISHED
Object Amsterdam–Paris 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: Amsterdam–Paris | Statement: [Dutch transport infrastructure, hasHighSpeedRailConnection, Amsterdam–Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amsterdam–Paris
Context triple: [Dutch transport infrastructure, hasHighSpeedRailConnection, Amsterdam–Paris]
  • A. Paris–Amsterdam chosen
    Paris–Amsterdam is a major international high-speed rail route linking the capitals of France and the Netherlands.
  • B. Paris–Brussels
    Paris–Brussels is a major international high-speed rail corridor linking the capitals of France and Belgium.
  • C. London–Amsterdam
    London–Amsterdam is a major international rail route connecting the capital cities of the United Kingdom and the Netherlands.
  • D. Frankfurt–Brussels
    Frankfurt–Brussels is a major international high-speed rail route linking Germany and Belgium, commonly served by InterCityExpress (ICE) trains.
  • E. Vienna–Amsterdam
    Vienna–Amsterdam is an international overnight train route connecting Austria’s capital with the Netherlands’ largest city.
  • 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.