Triple

T20574279
Position Surface form Disambiguated ID Type / Status
Subject Washington State Route 543 E505172 entity
Predicate truckRoute P3034 FINISHED
Object yes 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: yes | Statement: [Washington State Route 543, truckRoute, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: truckRoute
Context triple: [Washington State Route 543, truckRoute, yes]
  • 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
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • D. transportNetwork
    Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
  • E. transportCorridor chosen
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • 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_69e0b4b721588190993ac7b0a9be2736 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a9087af88190a4610ecb29f637ca completed April 20, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69e59ff0116c8190a163ff28ed01430a completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:39 a.m.