Triple
T19583910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goulds |
E490061
|
entity |
| Predicate | servedByRoad |
P385
|
FINISHED |
| Object | Route 10 |
—
|
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: Route 10 | Statement: [Goulds, servedByRoad, Route 10]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 10 Context triple: [Goulds, servedByRoad, Route 10]
-
A.
Route 10
Route 10 is a SEPTA subway–surface trolley line in Philadelphia that provides light rail service between Center City and the city’s western neighborhoods.
-
B.
Route 10
Route 10 is a public transit route that provides bus service connecting the Olneyville neighborhood with other parts of its metropolitan area.
-
C.
Route 10
chosen
Route 10 is a provincial highway in Newfoundland and Labrador, Canada, that serves coastal communities on the Avalon Peninsula, including providing access to the town of Mobile.
-
D.
Route 103
Route 103 is a state highway in Vermont that serves as a key north–south connector through the southeastern part of the state.
-
E.
Route 109
Route 109 is a state highway in Massachusetts that runs east–west through several suburbs of Boston, serving as a key commuter and regional connector road.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404f34b081908aeb9cc9a5ddf539 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.