Triple
T9454313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 202 |
E227975
|
entity |
| Predicate | signedAs |
P11811
|
FINISHED |
| Object | US 202 |
E227975
|
NE FINISHED |
How this triple was built (2 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 202 | Statement: [U.S. Route 202, signedAs, US 202]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US 202 Context triple: [U.S. Route 202, signedAs, US 202]
-
A.
US 202
chosen
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.
-
B.
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.
-
C.
US 20
US 20 is a major east–west United States highway that stretches from the Pacific Northwest to New England, serving as one of the country’s longest transcontinental routes.
-
D.
US 209
US 209 is a U.S. highway running through Pennsylvania and New York, connecting rural communities, small towns, and scenic areas in the northeastern United States.
-
E.
US 23
US 23 is a major north–south United States highway running from Florida to Michigan, serving as an important regional transportation corridor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8c7b3481909c1182b41d8c27a9 |
completed | April 1, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1227b4fc881908c03409f78de1a87 |
completed | April 4, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:52 p.m.