Triple

T23206928
Position Surface form Disambiguated ID Type / Status
Subject Washington, D.C. street numbering system E580483 entity
Predicate letteredStreetsIncrease P151351 FINISHED
Object away from Capitol 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: away from Capitol | Statement: [Washington, D.C. street numbering system, letteredStreetsIncrease, away from Capitol]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: letteredStreetsIncrease
Context triple: [Washington, D.C. street numbering system, letteredStreetsIncrease, away from Capitol]
  • A. isNumberedStreet
    Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
  • B. streetSet
    Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
  • C. hasNumberOfStreets
    Indicates the relationship that specifies how many streets are associated with or contained within a given entity.
  • D. numberOfConvergingStreets
    Indicates the count of distinct streets that meet or intersect at a particular junction or location.
  • E. cityStreetUsed
    Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
  • 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_69e24602ae1481908aaa6bc7ca493867 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1907d8be08190a100d99efaff9964 completed April 29, 2026, 5 a.m.
PD Predicate disambiguation batch_69effcccee508190a7ae311fdd319806 completed April 28, 2026, 12:18 a.m.
PDg Predicate description generation batch_69f01d8770d081908897c28b04e5faea completed April 28, 2026, 2:37 a.m.
Created at: April 17, 2026, 4:07 p.m.