Triple
T20696484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkman Road |
E508673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Orlando, Florida |
C43460
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: street in Orlando, Florida Context triple: [Kirkman Road, instanceOf, street in Orlando, Florida]
-
A.
street in San Juan, Puerto Rico
A street in San Juan, Puerto Rico is a public urban thoroughfare within the city’s historic or modern districts, lined with local residences, businesses, and cultural landmarks that facilitate vehicular and pedestrian movement.
-
B.
street in Buffalo, New York
A street in Buffalo, New York is a public roadway within the city’s urban grid that facilitates vehicular and pedestrian movement while connecting residential, commercial, and civic areas characteristic of Buffalo’s regional architecture and infrastructure.
-
C.
street in New York City
A street in New York City is a public urban thoroughfare lined with diverse buildings and infrastructure that supports vehicular, pedestrian, and commercial activity within the city's dense grid layout.
-
D.
street in Alpharetta, Georgia
A street in Alpharetta, Georgia is a public roadway within the city’s limits that provides access to residential, commercial, and community areas while connecting to the broader local and regional transportation network.
-
E.
road in Honolulu
A road in Honolulu is a paved transportation route within the city’s limits that supports vehicular, bicycle, and pedestrian travel while connecting local destinations and integrating with the island’s broader traffic and infrastructure network.
- F. None of above. chosen
Provenance (1 batch)
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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:10 p.m.