Triple
T1478882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio |
E30904
|
entity |
| Predicate | postalAbbreviation |
P43
|
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: [Ohio, postalAbbreviation, OH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OH Context triple: [Ohio, postalAbbreviation, OH]
-
A.
OH
chosen
OH is the official United States Postal Service abbreviation for the state of Ohio.
-
B.
OL
OL is a UK postcode area covering Oldham and surrounding parts of Greater Manchester and nearby regions in North West England.
-
C.
OKH
OKH (Oberkommando des Heeres) was the German Army High Command responsible for directing land operations for Nazi Germany during much of World War II.
-
D.
Ho
Ho are an indigenous Adivasi community of eastern India, primarily inhabiting parts of Jharkhand and Odisha, known for their Austroasiatic Ho language and distinct cultural traditions.
-
E.
OHC
OHC is the acronym for the Office of Habitat Conservation, a division focused on protecting and restoring vital natural habitats.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6739d2481909ea8d8e075f62cf3 |
completed | March 1, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad15aff1288190a3e36324d975d482 |
completed | March 8, 2026, 6:22 a.m. |
Created at: March 1, 2026, 8:11 p.m.