Triple
T333414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inwood |
E6672
|
entity |
| Predicate | hasStreetGridPattern |
P12506
|
FINISHED |
| Object | mix of grid and winding streets |
—
|
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: mix of grid and winding streets | Statement: [Inwood, hasStreetGridPattern, mix of grid and winding streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetGridPattern Context triple: [Inwood, hasStreetGridPattern, mix of grid and winding streets]
-
A.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
numberOfStripes
Indicates the count of distinct stripe markings associated with an entity.
-
D.
hasCommuterPattern
Indicates that there is a characteristic or recurring pattern in how an entity regularly travels between locations, typically for work or daily activities.
-
E.
drainagePattern
Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
- F. None of above. chosen
Provenance (4 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac4d9d081908a624464e450fb0e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.