Triple

T3351400
Position Surface form Disambiguated ID Type / Status
Subject Voorschoten E70500 entity
Predicate borderedBy P224 FINISHED
Object Wassenaar E174773 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: Wassenaar | Statement: [Voorschoten, borderedBy, Wassenaar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wassenaar
Context triple: [Voorschoten, borderedBy, Wassenaar]
  • A. Wassenaar chosen
    Wassenaar is an affluent coastal town in the western Netherlands known for its wooded estates, beaches, and role as a residential area for diplomats and expatriates.
  • B. Wateringen
    Wateringen is a town in the western Netherlands that forms part of the municipality of Westland in the province of South Holland.
  • C. Woudenberg
    Woudenberg is a small Dutch municipality and town located in the central Netherlands.
  • D. Nissewaard
    Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
  • E. Oranjewoud
    Oranjewoud is a historic estate and village in the Dutch province of Friesland, long associated with the royal House of Orange-Nassau.
  • 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_69ad85a4ef7c8190a29e2bbd6fa454e4 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb220721c81909eb4d8d35c923927 completed March 8, 2026, 5:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3252f3f248190bb61db5c4fd2781a completed March 12, 2026, 8:42 p.m.
Created at: March 8, 2026, 3:12 p.m.