Triple

T5221579
Position Surface form Disambiguated ID Type / Status
Subject 401 Derby E117880 entity
Predicate alsoKnownAs P39 FINISHED
Object Derby 401 E117880 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 401 | Statement: [401 Derby, alsoKnownAs, Derby 401]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Derby 401
Context triple: [401 Derby, alsoKnownAs, Derby 401]
  • A. 401 Derby chosen
    401 Derby is the Major League Soccer rivalry between Toronto FC and CF Montréal, named after the Ontario Highway 401 that connects the two cities.
  • B. Derby Racer
    Derby Racer is a classic wooden racing carousel-style amusement ride known for its high-speed, side-by-side galloping horses.
  • C. Intu Derby
    Intu Derby was a large shopping centre in Derby, England, formerly operated under the Intu Properties brand before being rebranded as Derbion.
  • D. The Derby
    The Derby is one of the most prestigious and historic flat horse races in the world, forming part of the British Classics and run annually at Epsom Downs.
  • E. A420 derby
    The A420 derby is a football rivalry match between Oxford United and Swindon Town, named after the road that links the two clubs’ home towns.
  • 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_69bd4465e03081909bfcfd7113062590 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7aba05b48190b6a7fc52ab3532f0 completed March 20, 2026, 4:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69beeff49d708190a042dfab473a9646 completed March 21, 2026, 7:22 p.m.
Created at: March 20, 2026, 1:48 p.m.