Triple

T22147435
Position Surface form Disambiguated ID Type / Status
Subject Indian Engineering Services E547323 entity
Predicate shortName P43 FINISHED
Object ESE 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: ESE | Statement: [Indian Engineering Services, shortName, ESE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ESE
Context triple: [Indian Engineering Services, shortName, ESE]
  • A. ESE chosen
    ESE is a highly competitive Indian national-level examination conducted by the Union Public Service Commission to recruit engineers for prestigious technical and managerial positions in various government departments and public sector organizations.
  • B. ESU
    ESU is a public university in Emporia, Kansas, known for its programs in education, business, and liberal arts.
  • C. ESU
    ESU is a specialized police emergency response unit that handles high-risk situations such as tactical operations, rescues, and hazardous incidents.
  • D. ES-LE
    ES-LE is the ISO 3166-2 subdivision code that identifies the province of León in Spain.
  • E. EES
    EES is the European Union’s Entry/Exit System, a large-scale IT platform that records and manages data on non-EU nationals crossing the external borders of the Schengen Area.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f156988190bc9a24a37418e849 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.