Triple
T280147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courthouse neighborhood |
E5334
|
entity |
| Predicate | streetPattern |
P3374
|
FINISHED |
| Object | urban street grid |
—
|
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: urban street grid | Statement: [Courthouse neighborhood, streetPattern, urban street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPattern Context triple: [Courthouse neighborhood, streetPattern, urban street grid]
-
A.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
C.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
D.
streetSectionOf
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
E.
streetNetwork
chosen
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.