Triple
T2841380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mar Vista |
E62475
|
entity |
| Predicate | hasTypeOfStreetPattern |
P12506
|
FINISHED |
| Object | residential 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: residential grid | Statement: [Mar Vista, hasTypeOfStreetPattern, residential grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfStreetPattern Context triple: [Mar Vista, hasTypeOfStreetPattern, residential grid]
-
A.
hasStreetGridPattern
chosen
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
-
B.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
C.
hasTrafficPattern
Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
-
D.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
E.
hasMedievalStreetPattern
Indicates that an area’s street layout follows or preserves a characteristic medieval pattern of routes, blocks, and spaces.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.