Triple
T5022847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Highway |
E112896
|
entity |
| Predicate | openedToMilitaryTraffic |
P61587
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Alaska Highway, openedToMilitaryTraffic, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToMilitaryTraffic Context triple: [Alaska Highway, openedToMilitaryTraffic, 1942]
-
A.
openedToRoadTraffic
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
B.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
C.
openedToGoodsTraffic
Indicates that a route, facility, or infrastructure was officially made available for the movement and handling of goods or freight traffic.
-
D.
openedToTrafficInYear
Indicates the year in which something, typically a transportation facility or route, was first officially opened for public traffic use.
-
E.
airportServesMilitaryTraffic
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73670578819099a56112950708a8 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:36 p.m.