Triple
T19001711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Road 836 |
E464968
|
entity |
| Predicate | hasOfficialAbbreviation |
P8075
|
FINISHED |
| Object |
SR 836
SR 836 is a major east–west expressway in Miami-Dade County, Florida, commonly known as the Dolphin Expressway.
|
E1353753
|
NE FINISHED |
How this triple was built (4 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 836 | Statement: [Florida State Road 836, hasOfficialAbbreviation, SR 836]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 836 Context triple: [Florida State Road 836, hasOfficialAbbreviation, SR 836]
-
A.
SR 88
SR 88 is a scenic California state highway that traverses the Sierra Nevada, connecting the Central Valley to mountain communities and recreational areas near the Nevada border.
-
B.
SR 431
SR 431 is a Nevada state highway that connects the Reno area to Lake Tahoe via the scenic Mount Rose Highway.
-
C.
SR 905
SR 905 is a California state highway in San Diego that connects Interstate 5 and Interstate 805 to the Otay Mesa Port of Entry at the U.S.–Mexico border.
-
D.
SR 80
SR 80 is a state highway designation commonly used in the United States for a numbered route that facilitates regional travel and connects various local roads and communities.
-
E.
SR 856
SR 856 is a state highway designation used for a specific numbered route within a U.S. state's road network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 836 Triple: [Florida State Road 836, hasOfficialAbbreviation, SR 836]
Generated description
SR 836 is a major east–west expressway in Miami-Dade County, Florida, commonly known as the Dolphin Expressway.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 836 Target entity description: SR 836 is a major east–west expressway in Miami-Dade County, Florida, commonly known as the Dolphin Expressway.
-
A.
SR 88
SR 88 is a scenic California state highway that traverses the Sierra Nevada, connecting the Central Valley to mountain communities and recreational areas near the Nevada border.
-
B.
SR 431
SR 431 is a Nevada state highway that connects the Reno area to Lake Tahoe via the scenic Mount Rose Highway.
-
C.
SR 905
SR 905 is a California state highway in San Diego that connects Interstate 5 and Interstate 805 to the Otay Mesa Port of Entry at the U.S.–Mexico border.
-
D.
SR 80
SR 80 is a state highway designation commonly used in the United States for a numbered route that facilitates regional travel and connects various local roads and communities.
-
E.
SR 856
SR 856 is a state highway designation used for a specific numbered route within a U.S. state's road network.
- F. None of above. chosen
Provenance (5 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d687cb2081909bf3ac761e292f22 |
completed | April 20, 2026, 7:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05b45dc7e88190a0bf79ea1bb18f99 |
completed | May 14, 2026, 11:39 a.m. |
| NEDg | Description generation | batch_6a05b5dfac0c8190b67921280d5ab1fe |
completed | May 14, 2026, 11:45 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a05b68aba3081908ca21d732e45f454 |
completed | May 14, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:01 p.m.