Triple
T26001841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas Highway 4 |
E646648
|
entity |
| Predicate | roadFunctionClass |
P1019
|
FINISHED |
| Object | rural major collector |
—
|
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: rural major collector | Statement: [Kansas Highway 4, roadFunctionClass, rural major collector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadFunctionClass Context triple: [Kansas Highway 4, roadFunctionClass, rural major collector]
-
A.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
B.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
C.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
E.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605770b2481908c1674952889f62f |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.