Triple
T16688476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 133 |
E405528
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | SR 133 |
E854928
|
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: SR 133 | Statement: [State Route 133, alsoKnownAs, SR 133]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 133 Context triple: [State Route 133, alsoKnownAs, SR 133]
-
A.
SR 133
chosen
SR 133 is a state highway in Maine that connects several central Maine communities and serves as a regional north–south transportation route.
-
B.
SR 132
SR 132 is a state highway in Maine that connects several small communities and links with other major regional routes.
-
C.
SR 131
SR 131 is a state highway in Maine that runs through Knox and Waldo counties, connecting several coastal and inland communities.
-
D.
SR 131
SR 131 is a short primary state highway in Virginia that serves as a connector route within the state's road network.
-
E.
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.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea75df481909a7ebb9b2a9d0afd |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d32e7b48190b7dd4660bed4789d |
completed | May 10, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:19 a.m.