Triple
T23929021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockton Street and Bayard Lane |
E602438
|
entity |
| Predicate | streetComponent |
P5397
|
FINISHED |
| Object | Stockton Street |
—
|
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: Stockton Street | Statement: [Stockton Street and Bayard Lane, streetComponent, Stockton Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetComponent Context triple: [Stockton Street and Bayard Lane, streetComponent, Stockton Street]
-
A.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
B.
streetOrArea
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
C.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
D.
streetSectionOf
chosen
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9a18248190b20991969921ecfd |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:54 p.m.