Triple
T10450445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Route 207 |
E246406
|
entity |
| Predicate | routeAbbreviation |
P75208
|
FINISHED |
| Object | OR 207 |
—
|
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: OR 207 | Statement: [Oregon Route 207, routeAbbreviation, OR 207]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAbbreviation Context triple: [Oregon Route 207, routeAbbreviation, OR 207]
-
A.
routeSymbol
chosen
Indicates that a particular symbol or code is used to represent or identify a specific route.
-
B.
significantlyShortensRouteBetween
Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
-
C.
missionAbbreviation
Indicates that one entity is the abbreviated or short-form designation of a mission represented by another entity.
-
D.
routeLetter
Indicates the action or process of directing or sending a letter along a specific path or through designated channels to its intended destination.
-
E.
typeOfAbbreviation
Indicates that one term is an abbreviation of a specific type or category (e.g., acronym, initialism) of another expression.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0a6a548190a54212912f618e4e |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.