Triple

T17526388
Position Surface form Disambiguated ID Type / Status
Subject Ameide E426805 entity
Predicate locatedNear P294 FINISHED
Object Lexmond NE NERFINISHED

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: Lexmond | Statement: [Ameide, locatedNear, Lexmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lexmond
Context triple: [Ameide, locatedNear, Lexmond]
  • A. Lexmond chosen
    Lexmond is a village in the Dutch province of Utrecht, known for its rural character and location along the River Lek.
  • B. Lawmond
    Lawmond is a Scottish family name recognized as a sept of Clan Lamont, a historic Highland clan from Argyll.
  • C. Simonds
    Simonds is a surname most notably associated with Canadian Lieutenant-General Guy Simonds, a prominent military commander during the Second World War.
  • D. Leandoer
    Leandoer is an alias of Swedish rapper, singer, and songwriter Yung Lean, known for pioneering the cloud rap and sad rap scenes.
  • E. Lundell
    Lundell is a Swedish surname most prominently associated with Ulf Lundell, a well-known rock musician, songwriter, and author.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452d6a2548190acf26f2d5d4aab66 completed April 19, 2026, 3:58 a.m.
Created at: April 10, 2026, 5:49 a.m.