Triple

T23212216
Position Surface form Disambiguated ID Type / Status
Subject Shimon Even E580626 entity
Predicate hasSurname P18 FINISHED
Object Even 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: Even | Statement: [Shimon Even, hasSurname, Even]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Even
Context triple: [Shimon Even, hasSurname, Even]
  • A. Even
    The Even are an Indigenous Siberian people traditionally engaged in reindeer herding, hunting, and fishing across northeastern Russia.
  • B. Even chosen
    Even is a surname most notably associated with Shimon Even, an influential Israeli computer scientist known for his foundational work in algorithms and graph theory.
  • C. Evens
    The Evens are an Indigenous Tungusic-speaking people of northeastern Siberia, traditionally known for reindeer herding, hunting, and a nomadic lifestyle in the Russian Far East.
  • D. Evjen
    Evjen is a village in Trøndelag county, Norway, located within the former municipality of Orkdal.
  • E. evenko
    evenko is a major Canadian entertainment company that promotes and produces concerts, festivals, and live events, particularly in and around Montreal.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f191620378819096362252c3b819b6 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:07 p.m.