Triple
T24554827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darlington F.C. |
E607483
|
entity |
| Predicate | reformedAs |
P1504
|
FINISHED |
| Object |
Darlington 1883
Darlington 1883 is an English football club formed by supporters to continue the legacy of the original Darlington F.C. after its financial collapse.
|
E1640934
|
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: Darlington 1883 | Statement: [Darlington F.C., reformedAs, Darlington 1883]
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: Darlington 1883 Triple: [Darlington F.C., reformedAs, Darlington 1883]
Generated description
Darlington 1883 is an English football club formed by supporters to continue the legacy of the original Darlington F.C. after its financial collapse.
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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f13d4c81909ffecf8c26d272f0 |
completed | April 30, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ff860cb088190822f75c1c1320b5f |
completed | May 22, 2026, 6:32 a.m. |
| NEDg | Description generation | batch_6a0ff8da6b308190adf2063821a84837 |
completed | May 22, 2026, 6:34 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ff9d952ec81908a5b2640c263e21d |
completed | May 22, 2026, 6:38 a.m. |
Created at: April 18, 2026, 2:27 a.m.