Triple
T32682710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Highway 99 |
E835630
|
entity |
| Predicate | providesRegionalAccessTo |
P78464
|
FINISHED |
| Object | Oakville area |
—
|
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: Oakville area | Statement: [Iowa Highway 99, providesRegionalAccessTo, Oakville area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesRegionalAccessTo Context triple: [Iowa Highway 99, providesRegionalAccessTo, Oakville area]
-
A.
accessesRegion
chosen
Indicates that one entity reaches, uses, or interacts with a specific geographic or logical region.
-
B.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
C.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
D.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
E.
hasAccessRegime
Indicates that one entity is subject to, governed by, or managed under a particular access control regime or set of access rules defined by another entity.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:09 a.m.