Triple
T33989991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reseda, Los Angeles |
E871515
|
entity |
| Predicate | streetGridAlignedWith |
P76449
|
FINISHED |
| Object | Los Angeles 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: Los Angeles street grid | Statement: [Reseda, Los Angeles, streetGridAlignedWith, Los Angeles street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetGridAlignedWith Context triple: [Reseda, Los Angeles, streetGridAlignedWith, Los Angeles street grid]
-
A.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
B.
streetGridExtendedFrom
Indicates that one street grid layout continues or expands outward from another street grid as its extension.
-
C.
streetGridRange
Indicates the span or extent of a street segment within a defined grid or block range in a street network.
-
D.
streetOrientedAlong
chosen
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
E.
hasStreetGridFeature
Indicates that a location or area possesses a specific characteristic or element of a street grid layout, such as a particular pattern, structure, or feature of its road 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70391c4c88190b3c5e91d46132c06 |
completed | May 3, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.