Triple
T9642546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Road 22 |
E233108
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 22 |
E242758
|
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 22 | Statement: [Florida State Road 22, abbreviation, SR 22]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 22 Context triple: [Florida State Road 22, abbreviation, SR 22]
-
A.
SR 22
chosen
SR 22 is a state highway in Florida that serves the Callaway area, providing a key route for local and regional traffic.
-
B.
SR 22
SR 22 is a state highway in Alabama that runs east–west across the central part of the state, connecting several rural communities and small towns.
-
C.
SR 224
SR 224 is a state highway in Washington that serves as a regional connector route in the south-central part of the state.
-
D.
SR 202
SR 202 is a state highway loop route commonly referred to as Loop 202.
-
E.
SR 228
SR 228 is a state highway in Florida that serves as a key route through the Jacksonville area, connecting local roads with major interstates and urban destinations.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7cda388190a38f96d78085f404 |
completed | April 1, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18252c1cc81908d33c9c55d645fbf |
completed | April 4, 2026, 9:27 p.m. |
Created at: March 30, 2026, 8:12 p.m.