Triple
T14572783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 186 |
E341960
|
entity |
| Predicate | routeConfiguration |
P32810
|
FINISHED |
| Object | two-lane highway |
—
|
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: two-lane highway | Statement: [Maine State Route 186, routeConfiguration, two-lane highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeConfiguration Context triple: [Maine State Route 186, routeConfiguration, two-lane highway]
-
A.
routeStructure
chosen
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
-
B.
routeSetting
Indicates that one entity configures or defines the path or course to be followed by another entity (such as a vehicle, signal, or data flow).
-
C.
routeSystem
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
D.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
E.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f33b1c8190bb447788bfd28d51 |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.