Triple
T35283904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopewell, Tennessee |
E1019018
|
entity |
| Predicate | locatedInU.S._region |
P56631
|
FINISHED |
| Object | East Tennessee |
E991480
|
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: East Tennessee | Statement: [Hopewell, Tennessee, locatedInU.S._region, East Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInU.S._region Context triple: [Hopewell, Tennessee, locatedInU.S._region, East Tennessee]
-
A.
locatedInUSRegion
chosen
Indicates that one entity is geographically situated within a specified region of the United States.
-
B.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
C.
includesUSRegions
Indicates that something contains or covers one or more specified regions within the United States.
-
D.
inUSStateRegion
Indicates that one entity is located within, or belongs to, a specific region of a U.S. state.
-
E.
isOneOfPrincipalRegionsOfUSCensusBureau
Indicates that a region is one of the primary geographic divisions defined by the U.S. Census Bureau for statistical and reporting purposes.
- F. None of above.
Provenance (4 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819daa9b48190991aa4377018c566 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.