Triple

T4484192
Position Surface form Disambiguated ID Type / Status
Subject Brouwershavense Gat E107195 entity
Predicate etymologyRelatedTo P453 FINISHED
Object Brouwershaven E302174 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: Brouwershaven | Statement: [Brouwershavense Gat, etymologyRelatedTo, Brouwershaven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brouwershaven
Context triple: [Brouwershavense Gat, etymologyRelatedTo, Brouwershaven]
  • A. Brouwershaven chosen
    Brouwershaven is a small historic town in the Dutch province of Zeeland, known for its maritime heritage and well-preserved old center.
  • B. Nieuwendam
    Nieuwendam is a historic neighborhood in the northern part of Amsterdam, known for its former village character and waterfront location along the IJ.
  • C. Borssele
    Borssele is a village in the Dutch province of Zeeland best known for hosting the Netherlands’ only commercial nuclear power plant.
  • D. Nieuwdorp
    Nieuwdorp is a small village in the Dutch province of Zeeland, located within the municipality of Borsele.
  • E. Hulst
    Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
  • 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_69bd43f84f788190a1383579c4a595be completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd52a54c6c8190a7421bea6e3c00f1 completed March 20, 2026, 1:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69d7faf8c1048190a136289a44a0930b completed April 9, 2026, 7:16 p.m.
Created at: March 20, 2026, 12:58 p.m.