Triple

T15058357
Position Surface form Disambiguated ID Type / Status
Subject Episcopal Diocese of San Diego E379555 entity
Predicate abbreviation P43 FINISHED
Object EDSD E379555 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: EDSD | Statement: [Episcopal Diocese of San Diego, abbreviation, EDSD]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EDSD
Context triple: [Episcopal Diocese of San Diego, abbreviation, EDSD]
  • A. EDSD chosen
    EDSD is the commonly used abbreviation for the Episcopal Diocese of San Diego, a regional jurisdiction of the Episcopal Church in Southern California.
  • B. ESE
    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.
  • C. EDDS
    EDDS is the ICAO airport code designating Stuttgart Airport in Germany.
  • D. ESU
    ESU is a public university in Emporia, Kansas, known for its programs in education, business, and liberal arts.
  • E. ESU
    ESU is a specialized police emergency response unit that handles high-risk situations such as tactical operations, rescues, and hazardous incidents.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dedee50afc8190bf7b0f4bbe8c60a3 completed April 15, 2026, 12:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69fea5c2fcec8190800d1bda82c7352e completed May 9, 2026, 3:10 a.m.
Created at: April 10, 2026, 3:01 a.m.