Triple

T11118484
Position Surface form Disambiguated ID Type / Status
Subject Fresno Flats E262956 entity
Predicate hasTransportRelation P11026 FINISHED
Object located along California State Route 41 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: located along California State Route 41 | Statement: [Fresno Flats, hasTransportRelation, located along California State Route 41]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportRelation
Context triple: [Fresno Flats, hasTransportRelation, located along California State Route 41]
  • A. hasTransportationRelation
    Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
  • B. hasTransportRoute chosen
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • C. hasTransportationElement
    Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
  • D. hasTransportationContext
    Indicates that there is a contextual relationship involving transportation modes, conditions, or circumstances relevant to the associated entities or event.
  • E. hasTransportCode
    Indicates that an entity is associated with a specific transport-related code used to identify or classify its mode, method, or details of transportation.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79af6fe448190b042c2e77b855b05 completed April 9, 2026, 12:26 p.m.
PD Predicate disambiguation batch_69d7441cf8188190b8095f622c923156 completed April 9, 2026, 6:15 a.m.
Created at: April 8, 2026, 9:28 p.m.