Triple

T4644936
Position Surface form Disambiguated ID Type / Status
Subject Hartelkering E101746 entity
Predicate locatedNear P294 FINISHED
Object Maasvlakte E111414 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: Maasvlakte | Statement: [Hartelkering, locatedNear, Maasvlakte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maasvlakte
Context triple: [Hartelkering, locatedNear, Maasvlakte]
  • A. Maasvlakte chosen
    Maasvlakte is a major artificial land and port expansion area on the North Sea coast of the Netherlands, forming part of the Port of Rotterdam.
  • B. IJmeer
    IJmeer is a shallow lake in the Netherlands, located east of Amsterdam and forming part of the IJsselmeer lake system.
  • C. Bijlmermeer
    Bijlmermeer is a residential neighborhood in Amsterdam, Netherlands, known for its large-scale modernist high-rise housing and diverse, multicultural population.
  • D. Zaanstad
    Zaanstad is a municipality in the province of North Holland in the Netherlands, known for its historic windmills, industrial heritage, and the picturesque Zaanse Schans area.
  • E. Ooltgensplaat
    Ooltgensplaat is a small village in the western Netherlands, located on the island of Goeree-Overflakkee and known for its historic harbor and rural character.
  • 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_69bd43d3bc7c81908f81fcf380476b0f completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6236e5488190a0ed6991c65c0a74 completed March 20, 2026, 3:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfadc5dc081908d56a49895105efb completed March 21, 2026, 1:56 a.m.
Created at: March 20, 2026, 1:14 p.m.