Triple

T6350358
Position Surface form Disambiguated ID Type / Status
Subject Carriage and Wagon Works E142853 entity
Predicate locatedIn P40 FINISHED
Object Derby, England E53520 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: Derby, England | Statement: [Carriage and Wagon Works, locatedIn, Derby, England]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Derby, England
Context triple: [Carriage and Wagon Works, locatedIn, Derby, England]
  • A. Derby, Derbyshire, England
    Derby, Derbyshire, England is a historic industrial city in the East Midlands known for its role in the Industrial Revolution and its long-standing engineering and railway heritage.
  • B. Derby
    Derby is a neighborhood within the Brazilian city of Recife, known for its central location and urban character.
  • C. Derby chosen
    Derby is a historic city in Derbyshire, England, known for its industrial heritage, particularly in railways and engineering.
  • D. Derby
    Derby is a small historic city in Connecticut known for its location at the confluence of the Housatonic and Naugatuck Rivers and its industrial heritage.
  • E. Derby
    Derby is a surname of English origin associated with notable historical figures such as American merchant Elias Hasket Derby.
  • 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_69c008d6dcbc8190aa1c2f1fd8916b42 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067bcec2c8190bb383605847b0f0b completed March 22, 2026, 10:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69c64ba8838c8190873ebe0ae9c0237d completed March 27, 2026, 9:19 a.m.
Created at: March 22, 2026, 4:31 p.m.