Triple

T36588351
Position Surface form Disambiguated ID Type / Status
Subject San Jose Avenue E902590 entity
Predicate connectsResidentialAreasTo P200891 FINISHED
Object regional freeway network 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: regional freeway network | Statement: [San Jose Avenue, connectsResidentialAreasTo, regional freeway network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsResidentialAreasTo
Context triple: [San Jose Avenue, connectsResidentialAreasTo, regional freeway network]
  • A. connectsResidentialArea
    Indicates a relationship where something serves as a link or route between one residential area and another.
  • B. connectsArea
    Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
  • C. connectsCentralAreaTo
    Indicates a relationship where one element serves as a link or pathway between a central area and another location or component.
  • D. connectsNeighborhoodsIn
    Indicates a relationship where something (such as a route, road, or service) links or provides direct access between two or more neighborhoods.
  • E. connectsCentralDistrictsWith
    Indicates a relationship where something serves as a link or route joining central districts to one another.
  • 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_69f76e6592e88190bac4eb00a46e9df9 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffb69812808190a751853b30183e65 completed May 9, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69ffb63bdda88190a9dd8426dc0bad43 completed May 9, 2026, 10:33 p.m.
PDg Predicate description generation batch_69ffb6976f84819098a9b14946591baa completed May 9, 2026, 10:35 p.m.
Created at: May 3, 2026, 4:11 p.m.