Triple
T4913610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elizabeth Way |
E110293
|
entity |
| Predicate | completedAsFreeway |
P59405
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Queen Elizabeth Way, completedAsFreeway, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedAsFreeway Context triple: [Queen Elizabeth Way, completedAsFreeway, 1970s]
-
A.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
B.
servedByFreeway
Indicates that a location or area is directly accessed or connected by a freeway.
-
C.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
D.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
E.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
- F. None of above. chosen
Provenance (4 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9dc41481908c0c398852e6819c |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.