Triple
T22907429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 81 (Georgia) |
E568485
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 81 |
—
|
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 81 | Statement: [SR 81 (Georgia), abbreviation, SR 81]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 81 Context triple: [SR 81 (Georgia), abbreviation, SR 81]
-
A.
SR 81
chosen
SR 81 is a state highway in Georgia that connects several communities in the eastern and north-central part of the state.
-
B.
SR 81
SR 81 is a state highway in Alabama that serves as a regional connector route within the state's road network.
-
C.
SR 8
SR 8 is a state highway in Maine that runs between Augusta and Solon, serving as a regional connector through central Maine.
-
D.
SR 8
SR 8 is a state highway in Washington that connects U.S. Route 101 near Elma to U.S. Route 12 near Olympia, serving as a key east–west corridor in the region.
-
E.
SR 8
SR 8 is a major north–south state highway in Ohio that connects the Akron area with Cleveland’s southeastern suburbs and other communities in northeastern Ohio.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18071b9ec81908922d5f046f7930a |
completed | April 29, 2026, 3:52 a.m. |
Created at: April 17, 2026, 3:42 p.m.