Triple
T2379532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocke County, Tennessee |
E46276
|
entity |
| Predicate | postalAbbreviation |
P43
|
FINISHED |
| Object | TN |
E94996
|
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: TN | Statement: [Cocke County, Tennessee, postalAbbreviation, TN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TN Context triple: [Cocke County, Tennessee, postalAbbreviation, TN]
-
A.
TN
chosen
TN is the official two-letter U.S. Postal Service abbreviation for the state of Tennessee.
-
B.
TN
TN is the official vehicle registration code used for the Indian state of Tamil Nadu.
-
C.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
-
D.
TON
TON is the three-letter ISO 3166-1 alpha-3 country code representing the Kingdom of Tonga.
-
E.
NST
NST is the standard time abbreviation for the Newfoundland Time Zone, which is uniquely offset by 3.5 hours from Coordinated Universal Time (UTC−3:30).
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b60c8c819080e4f682e4362a93 |
completed | March 7, 2026, 6:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aea8b23680819085e0c7da7b4da9e1 |
completed | March 9, 2026, 11:02 a.m. |
Created at: March 4, 2026, 7:57 p.m.