Triple
T6131560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hume Highway |
E136729
|
entity |
| Predicate | progressivelyUpgradedToFreewayStandard |
P21068
|
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: [Hume Highway, progressivelyUpgradedToFreewayStandard, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressivelyUpgradedToFreewayStandard Context triple: [Hume Highway, progressivelyUpgradedToFreewayStandard, late 20th century]
-
A.
completedAsFreeway
Indicates that a roadway segment has been fully constructed or upgraded to meet freeway standards, typically implying controlled access and grade-separated intersections.
-
B.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
C.
servedByFreeway
Indicates that a location or area is directly accessed or connected by a freeway.
-
D.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
E.
partlyUpgradedTo
chosen
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4f7ad8819096b09ddd312453fb |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.