Triple
T5852744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A316 road |
E130074
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object |
A310 road
The A310 road is a primary route in southwest London connecting the Richmond area with the A4 near Hounslow, serving local and through traffic between key suburban centres.
|
E2282640
|
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: A310 road | Statement: [A316 road, hasJunctionWith, A310 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: A310 road Triple: [A316 road, hasJunctionWith, A310 road]
Generated description
The A310 road is a primary route in southwest London connecting the Richmond area with the A4 near Hounslow, serving local and through traffic between key suburban centres.
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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0355038008190bf38980349b533e2 |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a94c988190b08b7fee382e3d00 |
completed | June 29, 2026, 7:50 a.m. |
| NEDg | Description generation | batch_6a42245f189881908ea69f7245cb3ca9 |
completed | June 29, 2026, 7:53 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a42249ab9408190a07e76742ff7526b |
completed | June 29, 2026, 7:54 a.m. |
Created at: March 22, 2026, 3:55 p.m.