Triple
T11728529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR |
E278838
|
entity |
| Predicate | exampleForm |
P12789
|
FINISHED |
| Object | SR 99 |
E151395
|
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 99 | Statement: [SR, exampleForm, SR 99]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 99 Context triple: [SR, exampleForm, SR 99]
-
A.
SR 99
chosen
SR 99 is a major north–south state highway in Washington that runs through the Seattle metropolitan area and parallels Interstate 5.
-
B.
SR 99
SR 99 is a major north–south highway running through California’s Central Valley, connecting cities such as Bakersfield, Fresno, and Sacramento.
-
C.
SR 91
SR 91 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
D.
Interstate 94
Interstate 94 is a major east–west U.S. Interstate Highway running from Montana to Michigan, serving key Midwestern cities such as Minneapolis–Saint Paul, Milwaukee, and Chicago.
-
E.
I-290
I-290 is a major Interstate Highway in northeastern Illinois that serves as a key commuter route connecting Chicago with its western suburbs.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68e9b70d08190aa74e612947317b5 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 8, 2026, 9:41 p.m.