Triple
T30709672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 5 in Oregon |
E781855
|
entity |
| Predicate | previousRouteCorridor |
P102403
|
FINISHED |
| Object | U.S. Route 99 in Oregon |
—
|
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: U.S. Route 99 in Oregon | Statement: [Interstate 5 in Oregon, previousRouteCorridor, U.S. Route 99 in Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRouteCorridor Context triple: [Interstate 5 in Oregon, previousRouteCorridor, U.S. Route 99 in Oregon]
-
A.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
B.
usesFormerRouteOf
chosen
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
C.
followedCorridor
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
D.
nearHistoricalRoute
Indicates that one entity is located close to a historically significant route or pathway.
-
E.
parallelTransportCorridor
Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:35 p.m.