Triple

T27322686
Position Surface form Disambiguated ID Type / Status
Subject California State Route 55 E689551 entity
Predicate northernConnectionName P69344 FINISHED
Object Riverside Freeway (SR 91) NE NERFINISHED

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: Riverside Freeway (SR 91) | Statement: [California State Route 55, northernConnectionName, Riverside Freeway (SR 91)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: northernConnectionName
Context triple: [California State Route 55, northernConnectionName, Riverside Freeway (SR 91)]
  • A. northernConnection
    Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
  • B. northernTerminusConnects chosen
    Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
  • C. connectsNorthTo
    Indicates that one entity serves as a connection or link from another entity to something located to its north.
  • D. northernTerminusVariant
    Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
  • E. northernBranch
    Indicates that one entity functions as the northern division, section, or offshoot of another entity.
  • 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_69ef355d4cb08190ab032c0a2e7d3753 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f627eb7f088190bdab06362c200d5c completed May 2, 2026, 4:35 p.m.
PD Predicate disambiguation batch_69f623a91b9c8190b2e2fdbc55cb89b6 completed May 2, 2026, 4:17 p.m.
Created at: April 27, 2026, 11:34 a.m.