Triple
T31694822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uptown entertainment district |
E808888
|
entity |
| Predicate | streetOrAreaIncludes |
P127309
|
FINISHED |
| Object | Telegraph Avenue corridor |
—
|
NE NERFINISHED |
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: Telegraph Avenue corridor | Statement: [Uptown entertainment district, streetOrAreaIncludes, Telegraph Avenue corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetOrAreaIncludes Context triple: [Uptown entertainment district, streetOrAreaIncludes, Telegraph Avenue corridor]
-
A.
streetOrArea
chosen
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
B.
streetOrAreaType
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
C.
streetAddressContains
Indicates that one street address string includes another address-related string as a substring or component.
-
D.
isCommonStreetNameIn
Indicates that a given name is frequently used as a street name within a specified geographic area or jurisdiction.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:09 p.m.