Triple
T609785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Cambridge |
E12071
|
entity |
| Predicate | hasStreetGrid |
P12506
|
FINISHED |
| Object | orthogonal 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: orthogonal street pattern | Statement: [East Cambridge, hasStreetGrid, orthogonal street pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetGrid Context triple: [East Cambridge, hasStreetGrid, orthogonal street pattern]
-
A.
hasStreetGridPattern
chosen
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
D.
hasStreetLayoutCenteredOn
Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
-
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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df68f2c8190a0ee9da4692b2a62 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.