Triple

T21858677
Position Surface form Disambiguated ID Type / Status
Subject Interstate 295 near Richmond, Virginia E539699 entity
Predicate truckRouteFunction P11026 FINISHED
Object preferred truck bypass of Richmond 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: preferred truck bypass of Richmond | Statement: [Interstate 295 near Richmond, Virginia, truckRouteFunction, preferred truck bypass of Richmond]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: truckRouteFunction
Context triple: [Interstate 295 near Richmond, Virginia, truckRouteFunction, preferred truck bypass of Richmond]
  • A. tradRoutes
    Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
  • B. tramRoutes
    Indicates that there exists a tram line or service that operates along a route connecting the related locations.
  • C. hasTransportRoute chosen
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • D. trailEndpoint
    Indicates that one entity marks the terminal point or ending location of a trail defined by another entity.
  • E. transportationFunction
    Indicates that one entity serves to move or carry another entity from one place to another.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0d63944d88190b6bd5e6ba4cc8ec1 completed April 28, 2026, 3:46 p.m.
PD Predicate disambiguation batch_69e6be9394f88190945ddd1dc004d29d completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 6:56 p.m.