Triple
T15682511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saluda County, South Carolina |
E377612
|
entity |
| Predicate | ISOCode |
P208
|
FINISHED |
| Object | US-SC |
E22331
|
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-SC | Statement: [Saluda County, South Carolina, ISOCode, US-SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-SC Context triple: [Saluda County, South Carolina, ISOCode, US-SC]
-
A.
SC State
SC State is a public, historically Black land-grant university located in Orangeburg, South Carolina.
-
B.
US-MS
US-MS is the ISO 3166-2 code representing the U.S. state of Mississippi.
-
C.
Carolinas
The Carolinas are a region of the southeastern United States comprising the states of North Carolina and South Carolina.
-
D.
South Carolina
chosen
South Carolina is a southeastern U.S. state known for its Atlantic coastline, historic cities like Charleston, and significant role in early American and Civil War history.
-
E.
La Carolina
La Carolina is a town and municipality in the province of Jaén in Andalusia, southern Spain, known historically as one of the New Towns of Sierra Morena founded in the 18th century.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ee4c8688190ae2fefb56171161a |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 10, 2026, 4:16 a.m.