Triple
T36500742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellows Falls |
E899317
|
entity |
| Predicate | onTransportationRoute |
P86982
|
FINISHED |
| Object | U.S. Route 5 |
—
|
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: U.S. Route 5 | Statement: [Bellows Falls, onTransportationRoute, U.S. Route 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onTransportationRoute Context triple: [Bellows Falls, onTransportationRoute, U.S. Route 5]
-
A.
situatedOnTransportRoute
chosen
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
B.
modernTransportRoute
Indicates a transportation route that uses contemporary or up-to-date modes, infrastructure, or standards for moving people or goods between locations.
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.