Triple
T1359899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reston Town Center |
E29073
|
entity |
| Predicate | hasStreetNetwork |
P3374
|
FINISHED |
| Object | grid-like street pattern |
—
|
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: grid-like street pattern | Statement: [Reston Town Center, hasStreetNetwork, grid-like street pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetNetwork Context triple: [Reston Town Center, hasStreetNetwork, grid-like street pattern]
-
A.
streetNetwork
chosen
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
isPublicRoadNetwork
Indicates that a given road network is officially designated for public use and accessible to the general public for transportation.
-
C.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
E.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c290db288190910fcfa17e902663 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.