Triple
T21646973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simplon Road |
E534245
|
entity |
| Predicate | openedToModernTraffic |
P16836
|
FINISHED |
| Object | early 1800s |
—
|
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: early 1800s | Statement: [Simplon Road, openedToModernTraffic, early 1800s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToModernTraffic Context triple: [Simplon Road, openedToModernTraffic, early 1800s]
-
A.
openedToRoadTraffic
chosen
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
B.
openedForThroughTraffic
Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
-
C.
openedToCivilianTraffic
Indicates that a previously restricted or closed route, facility, or infrastructure has been made accessible for use by civilian (non-military) traffic.
-
D.
reopenedToTraffic
Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
-
E.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591194dc8190a57b28eaddeceff5 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.