Triple

T13710848
Position Surface form Disambiguated ID Type / Status
Subject Glenne Headly E328765 entity
Predicate notableWork P4 FINISHED
Object ER E82125 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: ER | Statement: [Glenne Headly, notableWork, ER]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ER
Context triple: [Glenne Headly, notableWork, ER]
  • A. ER chosen
    ER is a critically acclaimed American medical drama television series that follows the personal and professional lives of staff in a busy Chicago emergency room.
  • B. ER
    ER is the zone code for Eastern Railway, one of the major railway zones of Indian Railways headquartered in Kolkata.
  • C. ER
    ER is the abbreviation used to designate the Eastern Region of British Rail, a major administrative division of the former British railway network covering eastern England.
  • D. ER
    ER is the IATA airline designator assigned to SereneAir, a Pakistani low-cost carrier.
  • E. ER
    ER is the standard abbreviation used for the Erie Otters, a junior ice hockey team in the Ontario Hockey League.
  • 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_69d80770b9bc81909f70c8c317d53cff completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dd43949e6c8190ae5e4fa119cde33a completed April 13, 2026, 7:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d54a68081908df25edf6d5df362 completed May 3, 2026, 7:09 p.m.
Created at: April 9, 2026, 9:54 p.m.