Triple
T21453552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 25 (Alabama) |
E529278
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 25 |
—
|
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: SR 25 | Statement: [SR 25 (Alabama), abbreviation, SR 25]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 25 Context triple: [SR 25 (Alabama), abbreviation, SR 25]
-
A.
SR 25
chosen
SR 25 is a state highway in Alabama that serves as a regional connector route through several counties and communities.
-
B.
SR 25
SR 25 is a scenic two-lane state highway in California that runs through rural agricultural areas and the Diablo Range, often used as an alternative route between the Bay Area and the Central Coast.
-
C.
SR 25
SR 25 is a primary state highway in Maine that connects the Portland area with several inland communities to the west.
-
D.
SR 255
SR 255 is a state highway in Maine that serves as a short connector route between local communities in Washington County.
-
E.
SR 259
SR 259 is a state highway in Maine that serves as a short connector route in the eastern part of the state.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d50b88819081a771596d0a2b2b |
completed | April 23, 2026, 9:43 a.m. |
Created at: April 16, 2026, 6:07 p.m.