Triple
T15809403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelmsford |
E383304
|
entity |
| Predicate | hasMajorRoadLink |
P385
|
FINISHED |
| Object | A12 road |
—
|
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: A12 road | Statement: [Chelmsford, hasMajorRoadLink, A12 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRoadLink Context triple: [Chelmsford, hasMajorRoadLink, A12 road]
-
A.
isMajorTransportLink
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
-
B.
isMajorTransportLinkIn
Indicates that a transport route or connection serves as a primary or significant transportation link within a specified area or region.
-
C.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- F. None of above.
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b529c6b481909664153ecc381f7c |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.