Triple
T13955928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 183 |
E335659
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 183
SR 183 is a state highway in Maine that serves as a local connector route within the state's road network.
|
E1074099
|
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 183 | Statement: [Maine State Route 183, abbreviation, SR 183]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 183 Context triple: [Maine State Route 183, abbreviation, SR 183]
-
A.
SR 181
SR 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
B.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
-
C.
SR 182
SR 182 is a state highway designated as State Route 182 within a U.S. state’s numbered road network.
-
D.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes 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 183 Triple: [Maine State Route 183, abbreviation, SR 183]
Generated description
SR 183 is a state highway in Maine that serves as a local connector route within the state's road network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 183 Target entity description: SR 183 is a state highway in Maine that serves as a local connector route within the state's road network.
-
A.
SR 181
SR 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
B.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
-
C.
SR 182
SR 182 is a state highway designated as State Route 182 within a U.S. state’s numbered road network.
-
D.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e78a4a481908e438745631a43c0 |
completed | April 14, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac8c06ec8190a6dfceab55da5b30 |
completed | May 6, 2026, 9:03 p.m. |
| NEDg | Description generation | batch_69fbafe60f1c8190bf9f98f83bdf05db |
completed | May 6, 2026, 9:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fbb04881f481909800f0183b30c370 |
completed | May 6, 2026, 9:19 p.m. |
Created at: April 9, 2026, 10:17 p.m.