Triple
T30702299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 29 (Massachusetts) |
E781643
|
entity |
| Predicate | routeNumberReplacedBy |
P22310
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Route 29 (Massachusetts), routeNumberReplacedBy, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNumberReplacedBy Context triple: [Route 29 (Massachusetts), routeNumberReplacedBy, 30]
-
A.
formerRouteNumber
chosen
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
B.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
C.
routeNumberFollowedBy
Indicates that one route number directly succeeds another in a defined ordering or sequence.
-
D.
routeNumberSignedAs
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
-
E.
replacedStation
Indicates that one station has taken the place of another station, typically succeeding it in function, service, or location.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68bdf2b3c81909578a19e0190e45d |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:34 p.m.