Triple

T12105335
Position Surface form Disambiguated ID Type / Status
Subject Working E288287 entity
Predicate title P38 FINISHED
Object Working E288287 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: Working | Statement: [Working, title, Working]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Working
Context triple: [Working, title, Working]
  • A. Working chosen
    "Working" is a musical by Stephen Schwartz that adapts Studs Terkel’s book of interviews into a series of vignettes exploring the lives and aspirations of everyday American workers.
  • B. Workmore
    Workmore is a small unincorporated rural community located in Telfair County, Georgia, United States.
  • C. Working Designs
    Working Designs was an American video game publisher best known for its high-quality, humor-infused localizations of Japanese role-playing games in the 1990s.
  • D. Prace
    Prace is a small village in the South Moravian Region of the Czech Republic, known for its proximity to the historic town of Slavkov u Brna (Austerlitz).
  • E. WFH
    WFH is the National Rail station code for Watford High Street railway station in Hertfordshire, England.
  • 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_69d6ab4a5c448190a110d1273314b21a completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d91561eaec819096ba00682d81f41a completed April 10, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f6795bf88190891acf918a432bef completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.