Triple
T8740139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington County, South Carolina |
E207477
|
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: [Lexington County, South Carolina, postalAbbreviation, SC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SC Context triple: [Lexington County, South Carolina, postalAbbreviation, SC]
-
A.
SC
SC is the vehicle registration code used on license plates for the German town of Schwabach in Bavaria.
-
B.
SC
chosen
SC is the standard two-letter postal abbreviation for the U.S. state of South Carolina.
-
C.
SC
SC is the commonly used abbreviation for Service Canada, the federal government agency that delivers a wide range of public services and benefits to Canadians.
-
D.
SC
SC is the official Indian Railways station code for Secunderabad Junction, a major railway hub in Telangana, India.
-
E.
SC
SC is the vehicle registration code used on license plates for vehicles registered in Częstochowa, a city in southern Poland.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d486e34819094a6c6ec26c047cf |
completed | March 31, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf42e7176c819097e313ed8e8ceb06 |
completed | April 3, 2026, 4:32 a.m. |
Created at: March 30, 2026, 6:38 p.m.