Triple

T9672594
Position Surface form Disambiguated ID Type / Status
Subject Interstate 214 (unused number) E234064 entity
Predicate isDecommissionedRoute P89547 FINISHED
Object no — 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: no | Statement: [Interstate 214 (unused number), isDecommissionedRoute, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isDecommissionedRoute
Context triple: [Interstate 214 (unused number), isDecommissionedRoute, no]
  • A. hasEliminationRoute
    Indicates that there exists a specific pathway or method by which something can be removed, discharged, or otherwise eliminated from a system or context.
  • B. isStrategicRouteFor
    Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
  • C. isPartOfRoute
    Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
  • D. isStandardRouteOn
    Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
  • E. isAccessRouteAround
    Indicates that one entity serves as an access route that goes around or circumvents another entity.
  • 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c6aa01c819083fc758470096ec2 completed April 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69ccd5b5d40c8190850ad7a351445f32 completed April 1, 2026, 8:22 a.m.
PDg Predicate description generation batch_69ccd9408c848190b84dd74d87f76273 completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:15 p.m.