Triple
T32893405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 91 |
E841399
|
entity |
| Predicate | formerNorthernConnection |
P200622
|
FINISHED |
| Object | Highway 4 (Alberta) |
—
|
NE NERFINISHED |
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: Highway 4 (Alberta) | Statement: [U.S. Route 91, formerNorthernConnection, Highway 4 (Alberta)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNorthernConnection Context triple: [U.S. Route 91, formerNorthernConnection, Highway 4 (Alberta)]
-
A.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
-
B.
northernContinuationOf
Indicates that one entity is a direct geographic or structural continuation of another entity toward the north.
-
C.
easternConnection
Indicates a relationship where one entity is connected to, aligned with, or positioned toward the east of another entity.
-
D.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
E.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69ff9bec9d748190869caebf6bf0c78f |
completed | May 9, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:18 a.m.