Triple
T12420001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresh Pond Parkway |
E296742
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Route 16 |
E71598
|
NE 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: Route 16 | Statement: [Fresh Pond Parkway, partOf, Route 16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 16 Context triple: [Fresh Pond Parkway, partOf, Route 16]
-
A.
Route 16
Route 16 is a major roadway in northern Chile that connects the inland city of Alto Hospicio with the coastal port city of Iquique.
-
B.
Route 16
chosen
Route 16 is a major east–west state highway in Massachusetts that connects several cities and towns in the Greater Boston area.
-
C.
Route 15
Route 15 is a major highway in New Brunswick, Canada, that serves as a key transportation corridor connecting the city of Moncton to surrounding regions.
-
D.
Route 15
Route 15 is a state highway designation used for a roadway in Massachusetts.
-
E.
Route 11
Route 11 is a designated roadway number used for a segment of Tokyo’s Shuto Expressway system known as the Daiba Line.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d6efd748190a5d9396a343e41e1 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f002b7c81909ee9d4ea3ea6d5f2 |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:55 p.m.