Triple

T18158695
Position Surface form Disambiguated ID Type / Status
Subject FSE E434698 entity
Predicate relatedTo P37 FINISHED
Object CHES 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: CHES | Statement: [FSE, relatedTo, CHES]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CHES
Context triple: [FSE, relatedTo, CHES]
  • A. CHES chosen
    CHES (Cryptographic Hardware and Embedded Systems) is a leading annual conference focused on the design and analysis of cryptographic hardware and security in embedded systems.
  • B. CHE
    CHE is the three-letter ISO 3166-1 alpha-3 country code for Switzerland.
  • C. CHE
    CHE is the acronym for the South Carolina Commission on Higher Education, the state agency responsible for coordinating and overseeing public higher education in South Carolina.
  • D. CHE
    CHE is a Christian university of applied sciences located in Ede, the Netherlands.
  • E. CHS
    CHS is the abbreviation for the Committee on Hemispheric Security, a body within the Organization of American States focused on security issues in the Western Hemisphere.
  • 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec02d9c81909ac6203b7d59c405 completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 10:30 a.m.