Triple

T20360912
Position Surface form Disambiguated ID Type / Status
Subject Allenham E496776 entity
Predicate locatedInFictional P7550 FINISHED
Object Devonshire 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: Devonshire | Statement: [Allenham, locatedInFictional, Devonshire]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devonshire
Context triple: [Allenham, locatedInFictional, Devonshire]
  • A. Devonshire chosen
    Devonshire is a prominent English noble house historically associated with the Dukes of Devonshire and the influential Cavendish family.
  • B. Devon
    Devon is a county in South West England known for its rugged coastlines, moorland national parks, and historic seaside towns.
  • C. Devon
    Devon is a residential neighbourhood located within the city of Fredericton in New Brunswick, Canada.
  • D. Devon
    Devon is a suburban community on the Philadelphia Main Line in Pennsylvania, best known for hosting the historic Devon Horse Show and Country Fair.
  • E. Devon
    Devon is a unisex given name of English origin, often associated with both people and places, including the English county of Devon.
  • 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678584294819093788ccf2fb8e588 completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.