Triple
T31611188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma State Highway 19 |
E806629
|
entity |
| Predicate | runsAcrossRegion |
P13729
|
FINISHED |
| Object | southern Oklahoma |
—
|
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: southern Oklahoma | Statement: [Oklahoma State Highway 19, runsAcrossRegion, southern Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAcrossRegion Context triple: [Oklahoma State Highway 19, runsAcrossRegion, southern Oklahoma]
-
A.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
B.
crossesRegion
chosen
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
C.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
D.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
E.
isRegionalCrossroads
Indicates that a place serves as a key junction where multiple regional routes, networks, or areas intersect and connect.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a873357481909a3499827e927cda |
completed | May 3, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:36 p.m.