Triple
T16172031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee's 2nd congressional district |
E392461
|
entity |
| Predicate | FECDistrictCode |
P120249
|
FINISHED |
| Object | TN02 |
—
|
LITERAL 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: TN02 | Statement: [Tennessee's 2nd congressional district, FECDistrictCode, TN02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FECDistrictCode Context triple: [Tennessee's 2nd congressional district, FECDistrictCode, TN02]
-
A.
federalDistrictNumber
Indicates the specific numbered federal electoral or administrative district associated with an entity.
-
B.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
C.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
D.
hasCongressionalDistrictCode
chosen
Indicates that an entity is associated with a specific congressional district identified by a particular district code.
-
E.
federalReserveDistrictNumber
Indicates the specific Federal Reserve district number with which an entity (such as a bank or location) is associated.
- F. None of above.
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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.