Triple
T11806589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia State Route 130 |
E280760
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 130 |
E811421
|
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: SR 130 | Statement: [Virginia State Route 130, abbreviation, SR 130]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 130 Context triple: [Virginia State Route 130, abbreviation, SR 130]
-
A.
SR 130
chosen
SR 130 is a state highway in Maine that runs through Lincoln County, connecting inland communities to the Pemaquid Point area on the Atlantic coast.
-
B.
SR 13
SR 13 is a north–south state highway in Ohio that runs between the city of Mansfield and the village of Huron, passing through several counties in the north-central part of the state.
-
C.
SR 135
SR 135 is a state highway in Maine that serves as a regional connector route between local communities.
-
D.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
-
E.
SR 133
SR 133 is a state highway in Maine that connects several central Maine communities and serves as a regional north–south transportation route.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5c8324481909a54852a9bb714e0 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f166f16a908190803cc986ce596aa1 |
completed | April 29, 2026, 2:03 a.m. |
Created at: April 8, 2026, 9:42 p.m.