Triple

T22595619
Position Surface form Disambiguated ID Type / Status
Subject Battle of Neerwinden (1693) E574671 entity
Predicate location P40 FINISHED
Object Neerwinden E574671 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: Neerwinden | Statement: [Battle of Neerwinden (1693), location, Neerwinden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neerwinden
Context triple: [Battle of Neerwinden (1693), location, Neerwinden]
  • A. Neerwinden chosen
    Neerwinden is a village in present-day Belgium known primarily as the site of two major 18th-century battles during the War of the Austrian Succession and the French Revolutionary Wars.
  • B. Zwanenveld
    Zwanenveld is a residential neighborhood in the Dukenburg district of Nijmegen in the Netherlands, known for its post-war urban planning and mixed housing.
  • C. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • D. Scherpenisse
    Scherpenisse is a village in the Dutch province of Zeeland, located on the island of Tholen.
  • E. Ruurlo
    Ruurlo is a village in the Dutch province of Gelderland, known for its historic estates 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_69e245bc11308190b69d794d5d1e0bb6 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f16268cb54819084a0f27ec0473f35 completed April 29, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0b3d61e0288190b644e5785f2379da completed May 18, 2026, 4:25 p.m.
Created at: April 17, 2026, 2:49 p.m.