Triple
T1536832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Dakota |
E32568
|
entity |
| Predicate | ISOCode |
P208
|
FINISHED |
| Object | US-SD |
E93985
|
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-SD | Statement: [South Dakota, ISOCode, US-SD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-SD Context triple: [South Dakota, ISOCode, US-SD]
-
A.
US-SD
chosen
US-SD is the ISO 3166-2 subdivision code that uniquely identifies the U.S. state of South Dakota.
-
B.
US-ME
US-ME is the ISO 3166-2 code representing the U.S. state of Maine.
-
C.
US
US is the IATA airline designator code assigned to the former American airline US Airways.
-
D.
US-RI
US-RI is the ISO 3166-2 subdivision code for the U.S. state of Rhode Island.
-
E.
UST
UST is the commonly used abbreviation for the United States Department of the Treasury, the federal executive department responsible for managing government revenue, producing currency, and formulating economic and financial policy.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90829e60081909d3f9f79585e080e |
completed | March 5, 2026, 4:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad295ed4508190be2c83496fa75bdf |
completed | March 8, 2026, 7:46 a.m. |
Created at: March 4, 2026, 7:26 p.m.