Triple

T9284435
Position Surface form Disambiguated ID Type / Status
Subject Midwest Connect E223151 entity
Predicate typicalRouteProfile P75679 FINISHED
Object regional routes within Midwestern states 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: regional routes within Midwestern states | Statement: [Midwest Connect, typicalRouteProfile, regional routes within Midwestern states]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalRouteProfile
Context triple: [Midwest Connect, typicalRouteProfile, regional routes within Midwestern states]
  • A. typicalProfile
    Indicates that an entity represents the standard or most representative profile or pattern for another entity.
  • B. primaryRouteType chosen
    Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
  • C. travelTimeTypical
    Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
  • D. notableRouteType
    Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
  • E. isMostCommonRouteTo
    Indicates that one route is the most frequently used or typical way to reach a particular destination or outcome compared to all other possible routes.
  • 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_69ca842123588190b3f2e1a69037d141 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd081e72988190917f425e64631837 completed April 1, 2026, 11:57 a.m.
PD Predicate disambiguation batch_69cc7a576ec88190bbb787eb82e2e539 completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:34 p.m.