Triple
T5464616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 275 |
E122676
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
US 275
US 275 is a U.S. highway running through parts of the Midwestern United States, primarily serving Nebraska, Iowa, and Missouri.
|
E521384
|
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: US 275 | Statement: [U.S. Route 275, abbreviation, US 275]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US 275 Context triple: [U.S. Route 275, abbreviation, US 275]
-
A.
US 23
US 23 is a major north–south United States highway running from Florida to Michigan, serving as an important regional transportation corridor.
-
B.
US 202
US 202 is a U.S. highway running through the northeastern United States, connecting cities in states such as Delaware, Pennsylvania, New Jersey, New York, and beyond.
-
C.
US 7
US 7 is a north–south U.S. highway in New England that runs from Connecticut through Massachusetts to Vermont, serving as a major regional route.
-
D.
US 201
US 201 is a U.S. highway in Maine that runs north–south from Brunswick to the Canadian border, serving as a key route through the state's interior.
-
E.
SR 27
SR 27 is a state highway in Maine that runs north–south, connecting coastal communities with inland towns and recreational areas.
- 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: US 275 Triple: [U.S. Route 275, abbreviation, US 275]
Generated description
US 275 is a U.S. highway running through parts of the Midwestern United States, primarily serving Nebraska, Iowa, and Missouri.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: US 275 Target entity description: US 275 is a U.S. highway running through parts of the Midwestern United States, primarily serving Nebraska, Iowa, and Missouri.
-
A.
US 23
US 23 is a major north–south United States highway running from Florida to Michigan, serving as an important regional transportation corridor.
-
B.
US 202
US 202 is a U.S. highway running through the northeastern United States, connecting cities in states such as Delaware, Pennsylvania, New Jersey, New York, and beyond.
-
C.
US 7
US 7 is a north–south U.S. highway in New England that runs from Connecticut through Massachusetts to Vermont, serving as a major regional route.
-
D.
US 201
US 201 is a U.S. highway in Maine that runs north–south from Brunswick to the Canadian border, serving as a key route through the state's interior.
-
E.
SR 27
SR 27 is a state highway in Maine that runs north–south, connecting coastal communities with inland towns and recreational areas.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9204504c81908d638da6f0e271a7 |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf415146988190823ab77b091231a1 |
completed | March 22, 2026, 1:09 a.m. |
| NEDg | Description generation | batch_69bf43a3f6f88190b3ea0c6760b498d1 |
completed | March 22, 2026, 1:19 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf4414beec8190a390481d802402b1 |
completed | March 22, 2026, 1:21 a.m. |
Created at: March 20, 2026, 2:08 p.m.