Triple
T9511649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 422 |
E229410
|
entity |
| Predicate | stateAbbreviation |
P2461
|
FINISHED |
| Object | OH |
E133232
|
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: OH | Statement: [U.S. Route 422, stateAbbreviation, OH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OH Context triple: [U.S. Route 422, stateAbbreviation, OH]
-
A.
OH
chosen
OH is the official United States Postal Service abbreviation for the state of Ohio.
-
B.
HO
HO is the vehicle registration code used on license plates for the city and district of Hof in Upper Franconia, Germany.
-
C.
HO
HO is the stock ticker symbol for Thales Group, a major French multinational company specializing in aerospace, defense, security, and transportation technologies.
-
D.
OL
OL is the vehicle registration code for the city of Oldenburg in the German state of Lower Saxony.
-
E.
OL
OL is the post-nominal abbreviation used by recipients of Papua New Guinea’s Order of Logohu, a national honor recognizing distinguished service.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98699b788190b1a475e1b1883584 |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d13a37c7ec8190a24ae0eec76b4f67 |
completed | April 4, 2026, 4:20 p.m. |
Created at: March 30, 2026, 7:58 p.m.