Triple
T30304628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A406 Southend Road |
E770744
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object |
Southend Road
Southend Road is a major roadway in London that forms part of the A406 North Circular route.
|
E2293645
|
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: Southend Road | Statement: [A406 Southend Road, hasName, Southend Road]
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: Southend Road Triple: [A406 Southend Road, hasName, Southend Road]
Generated description
Southend Road is a major roadway in London that forms part of the A406 North Circular route.
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68166930881909608eece2bc5f055 |
completed | May 2, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7ae7c101488190a192ba9bb8570486 |
completed | Aug. 11, 2026, 9:13 a.m. |
| NEDg | Description generation | batch_6a7ae80cfb2081909b39746d64d4a675 |
completed | Aug. 11, 2026, 9:14 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a7ae961cc708190ac3b20e200605c4e |
completed | Aug. 11, 2026, 9:20 a.m. |
Created at: April 29, 2026, 7:49 p.m.