Triple
T32616915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henderson, Tennessee |
E833808
|
entity |
| Predicate | distanceToJacksonTennesseeInMiles |
—
|
GENERATED |
| Object | about 15 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToJacksonTennesseeInMiles Context triple: [Henderson, Tennessee, distanceToJacksonTennesseeInMiles, about 15]
-
A.
distanceToJackson
chosen
Indicates the spatial distance or separation between a given entity and Jackson.
-
B.
distanceToMemphisApproxMiles
Indicates an approximate distance, measured in miles, between a given entity’s location and the city of Memphis.
-
C.
distanceToNashvilleInMilesApprox
Indicates the approximate distance, measured in miles, between a given entity’s location and Nashville.
-
D.
distanceToChattanooga
Indicates the spatial distance between a given entity and the location of Chattanooga.
-
E.
distanceToKnoxville
Indicates the spatial distance between a given entity’s location and the city of Knoxville.
- F. None of above.
Provenance (1 batch)
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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.