Triple
T4192411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spalding |
E89064
|
entity |
| Predicate | hasTransport |
P1298
|
FINISHED |
| Object | A16 road |
E445721
|
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: A16 road | Statement: [Spalding, hasTransport, A16 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A16 road Context triple: [Spalding, hasTransport, A16 road]
-
A.
A16 road
chosen
The A16 road is a major route in eastern England that runs through Lincolnshire and connects key towns such as Grimsby, Louth, and Spalding.
-
B.
A15 road
The A15 road is a major north–south route in eastern England that connects Peterborough to Hull, passing through Lincoln and serving as an important regional transport corridor.
-
C.
A14 road
The A14 road is a major trunk route in England that links the Midlands to the East Coast, serving as a key freight and commuter corridor including through Cambridgeshire.
-
D.
A13 road
The A13 road is a major east–west route in southern England connecting central London with the Thames Gateway and Essex.
-
E.
A12 road
The A12 road is a major trunk route in eastern England that connects London with coastal towns in Essex and Suffolk before continuing toward Norfolk.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af034169f88190a8eb170ba6008b79 |
completed | March 9, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f12f646ec88190ab4745c52798b599 |
completed | April 28, 2026, 10:06 p.m. |
Created at: March 9, 2026, 3:46 p.m.