Triple
T37941151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota state highway system |
E946488
|
entity |
| Predicate | neighboringStateConnection |
P115309
|
FINISHED |
| Object | Minnesota state highway system |
—
|
NE NERFINISHED |
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: Minnesota state highway system | Statement: [North Dakota state highway system, neighboringStateConnection, Minnesota state highway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringStateConnection Context triple: [North Dakota state highway system, neighboringStateConnection, Minnesota state highway system]
-
A.
connectsStates
chosen
Indicates a relationship where one entity serves as a link or route that joins two or more states together.
-
B.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
C.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
D.
stateRouteConnection
Indicates a relationship where a state-level route connects or links two locations or transportation segments.
-
E.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:20 p.m.