Triple

T3134162
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam–Rhine Canal E65486 entity
Predicate nearCity P350 FINISHED
Object Maarssen E522008 NE FINISHED

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: Maarssen | Statement: [Amsterdam–Rhine Canal, nearCity, Maarssen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maarssen
Context triple: [Amsterdam–Rhine Canal, nearCity, Maarssen]
  • A. Maarssen chosen
    Maarssen is a town in the Dutch province of Utrecht, situated along the river Vecht and functioning largely as a residential and commuter community near the city of Utrecht.
  • B. Maasdijk
    Maasdijk is a village in the Dutch province of South Holland, known for its greenhouse horticulture and proximity to the North Sea coast.
  • C. Maassluis
    Maassluis is a historic port town in the province of South Holland in the Netherlands, situated along the Nieuwe Waterweg west of Rotterdam.
  • D. Hardinxveld-Giessendam
    Hardinxveld-Giessendam is a Dutch town and municipality known for its shipbuilding industry and location along the river Merwede in the province of South Holland.
  • E. Deurne
    Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ad8581c25c8190b0d85ba9b9baa531 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada562540081908627950dd0b56a1e completed March 8, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c01f036b7881908a555ff18ca5a9af completed March 22, 2026, 4:55 p.m.
Created at: March 8, 2026, 3:05 p.m.