Triple
T1074127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redhill |
E23394
|
entity |
| Predicate | roadLink |
P11435
|
FINISHED |
| Object | A25 road |
E19429
|
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: A25 road | Statement: [Redhill, roadLink, A25 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A25 road Context triple: [Redhill, roadLink, A25 road]
-
A.
A25 road
chosen
The A25 road is an important east–west route in South East England that runs through Surrey and connects several towns between Guildford and Sevenoaks.
-
B.
A22 road
The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
-
C.
A21 road
The A21 road is a major route in southeast England that connects London with Hastings on the south coast, passing through Kent and East Sussex.
-
D.
A23 road
The A23 road is a major route in southern England connecting London to Brighton, serving as a key corridor between the capital and the south coast.
-
E.
A27 road
The A27 road is a major east–west trunk route along England’s south coast, linking key towns and cities between Hampshire and East Sussex.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bb7320f88190a8428946541df157 |
completed | March 1, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf01f74c8190938753276629fdf3 |
completed | March 10, 2026, 5:41 a.m. |
Created at: March 1, 2026, 7:42 p.m.