Triple
T18733360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 255 |
E458095
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 255
SR 255 is a state highway in Maine that serves as a short connector route between local communities in Washington County.
|
E1340551
|
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 255 | Statement: [Maine State Route 255, abbreviation, SR 255]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 255 Context triple: [Maine State Route 255, abbreviation, SR 255]
-
A.
SR 525
SR 525 is a state highway in Washington that connects the Mukilteo ferry terminal to Interstate 5 and serves as a key route through Snohomish County.
-
B.
SR 25
SR 25 is a state highway in Alabama that serves as a regional connector route through several counties and communities.
-
C.
SR 25
SR 25 is a scenic two-lane state highway in California that runs through rural agricultural areas and the Diablo Range, often used as an alternative route between the Bay Area and the Central Coast.
-
D.
SR 205
SR 205 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
E.
SR 502
SR 502 is a state highway in New Mexico that serves as a key route connecting Los Alamos to other major roads in the region.
- 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 255 Triple: [Maine State Route 255, abbreviation, SR 255]
Generated description
SR 255 is a state highway in Maine that serves as a short connector route between local communities in Washington County.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 255 Target entity description: SR 255 is a state highway in Maine that serves as a short connector route between local communities in Washington County.
-
A.
SR 525
SR 525 is a state highway in Washington that connects the Mukilteo ferry terminal to Interstate 5 and serves as a key route through Snohomish County.
-
B.
SR 25
SR 25 is a state highway in Alabama that serves as a regional connector route through several counties and communities.
-
C.
SR 25
SR 25 is a scenic two-lane state highway in California that runs through rural agricultural areas and the Diablo Range, often used as an alternative route between the Bay Area and the Central Coast.
-
D.
SR 205
SR 205 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
E.
SR 502
SR 502 is a state highway in New Mexico that serves as a key route connecting Los Alamos to other major roads in the region.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d791ab88190b333503f9b1ad0c0 |
completed | April 20, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05325dbcc08190b289e2c7a6175509 |
completed | May 14, 2026, 2:24 a.m. |
| NEDg | Description generation | batch_6a05344331fc81908d85322432c18ebe |
completed | May 14, 2026, 2:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a053548c4248190833a6e57de308c83 |
completed | May 14, 2026, 2:36 a.m. |
Created at: April 10, 2026, 11:51 a.m.