Triple

T37383890
Position Surface form Disambiguated ID Type / Status
Subject Rushden & Diamonds F.C. E928511 entity
Predicate successorClub P78 FINISHED
Object AFC Rushden & Diamonds
AFC Rushden & Diamonds is an English football club formed by supporters to continue the legacy of the former Rushden & Diamonds F.C. after its dissolution.
E2228259 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: AFC Rushden & Diamonds | Statement: [Rushden & Diamonds F.C., successorClub, AFC Rushden & Diamonds]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: AFC Rushden & Diamonds
Triple: [Rushden & Diamonds F.C., successorClub, AFC Rushden & Diamonds]
Generated description
AFC Rushden & Diamonds is an English football club formed by supporters to continue the legacy of the former Rushden & Diamonds F.C. after its dissolution.

Provenance (5 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_69f76eb9e66881908534cf22d04c3b5a completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8d3178dc8190ada8e3bbef965d7d completed May 6, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a408c22e7708190b62c99e1bdc8de2e completed June 28, 2026, 2:51 a.m.
NEDg Description generation batch_6a408d7b754c8190913cb8cdb1b1839c completed June 28, 2026, 2:56 a.m.
NED2 Entity disambiguation (via description) batch_6a408dbf8c9c8190854708a2ce7fd32e completed June 28, 2026, 2:58 a.m.
Created at: May 3, 2026, 4:16 p.m.