Triple
T18930031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A14 road |
E463079
|
entity |
| Predicate | openedAsTrunkRoute |
P34699
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [A14 road, openedAsTrunkRoute, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTrunkRoute Context triple: [A14 road, openedAsTrunkRoute, late 20th century]
-
A.
openedAsTrunkRoad
chosen
Indicates that a road was originally opened or designated for use as a main trunk road in the highway network.
-
B.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
C.
openedForTram
Indicates that something (such as a route, track, or facility) is available and in use for tram operations.
-
D.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
-
E.
isOnTrunkLine
Indicates that something is located on, or directly connected to, a primary or main trunk line within a network or system.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bfaee881908d701c5a05528939 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.