Triple
T25678600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Street area |
E643874
|
entity |
| Predicate | formerNameOfMainRoad |
P168026
|
FINISHED |
| Object | Park 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: Park Street | Statement: [Park Street area, formerNameOfMainRoad, Park Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfMainRoad Context triple: [Park Street area, formerNameOfMainRoad, Park Street]
-
A.
previousStreetName
chosen
Indicates that one street name was formerly used for a street that now has a different, current name.
-
B.
hasFormerStreetName
Indicates that an entity (such as a street or place) was previously known by a different street name.
-
C.
formerConstituentHighway
Indicates that a highway was once part of, but is no longer included in, another highway or highway system.
-
D.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
E.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 21, 2026, 7:43 p.m.