Triple
T19886146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caruthersville, Missouri |
E477904
|
entity |
| Predicate | roadTransportAccess |
P12181
|
FINISHED |
| Object | served by regional highways |
—
|
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: served by regional highways | Statement: [Caruthersville, Missouri, roadTransportAccess, served by regional highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTransportAccess Context triple: [Caruthersville, Missouri, roadTransportAccess, served by regional highways]
-
A.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
B.
transportNetwork
chosen
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
C.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
D.
transportRisk
Indicates the level or type of potential loss, damage, or adverse outcome associated with transporting something from one place to another.
-
E.
transportationAccessPlan
Indicates that there is a planned or defined arrangement for how transportation services or infrastructure will be accessed or used.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65909fe0481908e22b60d04fe2b11 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.