Triple
T16239666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 1 |
E394208
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | SR 1 |
E124044
|
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 1 | Statement: [State Route 1, alsoKnownAs, SR 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 1 Context triple: [State Route 1, alsoKnownAs, SR 1]
-
A.
SR 1
chosen
SR 1 is a major north–south state highway in Georgia that largely follows the route of U.S. Route 27 across the state.
-
B.
SR 1
SR 1 is a designation for a Florida state highway route that forms part of the state's numbered road network.
-
C.
SR 11
SR 11 is a planned and partially completed state highway intended to serve as a transportation corridor within its state’s road network.
-
D.
SR 16
SR 16 is a primary state highway in Washington that connects the Tacoma area to the Kitsap Peninsula, including the Tacoma Narrows Bridge crossing.
-
E.
SR 16
SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455d5270819090171d4207223a28 |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000edaf76c8190acc01f58845e570a |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.