Triple
T19937679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 263 |
E479215
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 263
SR 263 is a state highway in Maine that serves as a short connector route within the state's numbered road network.
|
E1403284
|
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 263 | Statement: [Maine State Route 263, abbreviation, SR 263]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 263 Context triple: [Maine State Route 263, abbreviation, SR 263]
-
A.
SR 261
SR 261 is a state highway in the United States designated as State Route 261.
-
B.
SR 267
SR 267 is a California state highway that connects the Lake Tahoe area near Kings Beach with the town of Truckee, providing access over the Sierra Nevada.
-
C.
SR 267
SR 267 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
D.
SR 262
SR 262 is a state highway in Maine that serves as a short connector route between local communities in the northern part of the state.
-
E.
SR 266
SR 266 is a state highway in Georgia that serves as a regional connector route within the 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 263 Triple: [Maine State Route 263, abbreviation, SR 263]
Generated description
SR 263 is a state highway in Maine that serves as a short connector route within the state's numbered road network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 263 Target entity description: SR 263 is a state highway in Maine that serves as a short connector route within the state's numbered road network.
-
A.
SR 261
SR 261 is a state highway in the United States designated as State Route 261.
-
B.
SR 267
SR 267 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
C.
SR 267
SR 267 is a California state highway that connects the Lake Tahoe area near Kings Beach with the town of Truckee, providing access over the Sierra Nevada.
-
D.
SR 262
SR 262 is a state highway in Maine that serves as a short connector route between local communities in the northern part of the state.
-
E.
SR 266
SR 266 is a state highway in Georgia that serves as a regional connector route within the 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a17fb2c8190b3aaae88e741648a |
completed | April 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07f6ec40f88190926f1330300fdc61 |
completed | May 16, 2026, 4:47 a.m. |
| NEDg | Description generation | batch_6a07f9c8f6c08190a949ebbb70b08d01 |
completed | May 16, 2026, 4:59 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a07fb3a144c8190b9bf2148702d6b6c |
completed | May 16, 2026, 5:06 a.m. |
Created at: April 10, 2026, 1:53 p.m.