Triple
T3376290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorchester County, South Carolina |
E71072
|
entity |
| Predicate | postalAbbreviation |
P43
|
FINISHED |
| Object | SC |
E120087
|
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: SC | Statement: [Dorchester County, South Carolina, postalAbbreviation, SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SC Context triple: [Dorchester County, South Carolina, postalAbbreviation, SC]
-
A.
SC
chosen
SC is the standard two-letter postal abbreviation for the U.S. state of South Carolina.
-
B.
SC
SC is the official Indian Railways station code for Secunderabad Junction, a major railway hub in Telangana, India.
-
C.
.sc
.sc is the country code top-level domain (ccTLD) assigned to the Republic of Seychelles for use in internet addresses.
-
D.
CR
CR is the two-letter ISO 3166-1 alpha-2 country code representing Costa Rica.
-
E.
CR
CR was the stock ticker symbol for Conrail, a major U.S. freight railroad company formed from bankrupt Northeastern railroads and later acquired by CSX and Norfolk Southern.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e776508190bc123fb17b36f062 |
completed | March 8, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b334465b50819080c6f23eaa6583be |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:13 p.m.