Triple

T21183396
Position Surface form Disambiguated ID Type / Status
Subject Maarssen E522008 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Maarssen-dorp 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: Maarssen-dorp | Statement: [Maarssen, hasNeighbourhood, Maarssen-dorp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maarssen-dorp
Context triple: [Maarssen, hasNeighbourhood, Maarssen-dorp]
  • 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. Maashorst
    Maashorst is a municipality in the Dutch province of North Brabant, known for its extensive nature reserve featuring heathlands, forests, and free-roaming large grazers.
  • C. Maarsbergen
    Maarsbergen is a village in the Dutch province of Utrecht, known for its rural character, historic estates, and location near major transport routes and the Utrechtse Heuvelrug national park.
  • D. Geersdijk
    Geersdijk is a small village located on the island of North Beveland in the Dutch province of Zeeland.
  • E. Moosseedorf
    Moosseedorf is a municipality in the canton of Bern in Switzerland, known for its proximity to the city of Bern and the nearby Moossee lake.
  • 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_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7301f7f1c81908686866fdee57127 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 3:05 p.m.