Triple
T21525137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A30 road |
E531074
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | A30 |
—
|
NE NERFINISHED |
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: A30 | Statement: [A30 road, roadNumber, A30]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A30 Context triple: [A30 road, roadNumber, A30]
-
A.
A30
chosen
The A30 is a major trunk road in southern England that runs from London to Land's End in Cornwall, serving as an important route across the southwest.
-
B.
A303
The A303 is a major trunk road in southern England that links the M3 motorway near Basingstoke to the A30 in Devon, passing close to landmarks such as Stonehenge.
-
C.
A33
A33 is a major road in southern England that runs between Reading and Southampton, serving as an important regional transport route.
-
D.
A302
A302 is a key section of London's Inner Ring Road, linking central routes across Westminster and the South Bank.
-
E.
A31
A31 is a major European motorway designation used for important highway routes in countries such as France and Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee885073888190ae49f967f72acbf8 |
completed | April 26, 2026, 9:49 p.m. |
Created at: April 16, 2026, 6:26 p.m.