Triple
T33538961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa secondary road system |
E859018
|
entity |
| Predicate | roadTypeIncluded |
P1019
|
FINISHED |
| Object | gravel roads |
—
|
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: gravel roads | Statement: [Iowa secondary road system, roadTypeIncluded, gravel roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeIncluded Context triple: [Iowa secondary road system, roadTypeIncluded, gravel roads]
-
A.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadTypeAtSquare
Indicates the specific type or classification of road present at a given square or location in a spatial grid or map.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
E.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.