Triple
T20629838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Rutledge |
E506922
|
entity |
| Predicate | routeGroup |
P140835
|
FINISHED |
| Object | Missouri corridor |
—
|
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: Missouri corridor | Statement: [Ann Rutledge, routeGroup, Missouri corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeGroup Context triple: [Ann Rutledge, routeGroup, Missouri corridor]
-
A.
routeArea
Indicates that an area is associated with, covered by, or traversed by a particular route.
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
routeUnder
Indicates that one route passes beneath another route or structure, typically at an underpass or similar crossing.
-
D.
routeSystem
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
E.
routeStructure
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
- F. None of above. chosen
Provenance (4 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad09c71881909698d3c2576cc181 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.