Triple
T15810822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hook Junction with A3 |
E383346
|
entity |
| Predicate | primaryRoadClass |
P1019
|
FINISHED |
| Object | trunk road (A3) |
—
|
LITERAL 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: trunk road (A3) | Statement: [Hook Junction with A3, primaryRoadClass, trunk road (A3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoadClass Context triple: [Hook Junction with A3, primaryRoadClass, trunk road (A3)]
-
A.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
C.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
arterialRoad
Indicates that a road functions as a primary high-capacity route that channels major traffic flows between different areas of a transport network.
- 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_69e0b52aae14819091de08630e7e1d1a |
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:49 a.m.