Triple

T11406920
Position Surface form Disambiguated ID Type / Status
Subject Battle of Landen E270261 entity
Predicate location P40 FINISHED
Object Landen E858326 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: Landen | Statement: [Battle of Landen, location, Landen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Landen
Context triple: [Battle of Landen, location, Landen]
  • A. Landen chosen
    Landen is a historic town in present-day Belgium, traditionally associated with the early medieval Frankish nobleman Pepin of Landen.
  • B. Leeland
    Leeland is a contemporary Christian worship band known for its melodic rock sound and spiritually themed lyrics.
  • C. Kingsland
    Kingsland is a vibrant inner-city suburb of Auckland, New Zealand, known for its cafes, bars, and proximity to Eden Park stadium.
  • D. Lufton
    Lufton is a fictional aristocratic family name most notably associated with the character Lord Lufton in Anthony Trollope’s Barsetshire novels.
  • E. Lantzville
    Lantzville is a small coastal community and district municipality on central Vancouver Island in British Columbia, Canada, known for its residential character and seaside setting.
  • 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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8014c820c81908538ba4a08e13230 completed April 9, 2026, 7:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69e58d56608481908dbb19daa2abfc0a completed April 20, 2026, 2:20 a.m.
Created at: April 8, 2026, 9:34 p.m.