Triple

T15083010
Position Surface form Disambiguated ID Type / Status
Subject Moerdijk E360196 entity
Predicate containsSettlement P847 FINISHED
Object Moerdijk village E360196 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: Moerdijk village | Statement: [Moerdijk, containsSettlement, Moerdijk village]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moerdijk village
Context triple: [Moerdijk, containsSettlement, Moerdijk village]
  • A. Scharendijke
    Scharendijke is a village in the Dutch province of Zeeland, known as a popular base for water sports and diving in the Grevelingen and North Sea area.
  • B. 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.
  • C. Veldhoven
    Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
  • D. Moerdijk chosen
    Moerdijk is a municipality and industrial port area in the southern Netherlands, known for its large logistics and chemical industry complexes.
  • E. Nijverdal
    Nijverdal is a town in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
  • 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0027450a48190a84588b6aaf84ebf completed April 15, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7e188448190b855ace5ab390646 completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:03 a.m.