Triple
T36904443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport, Tennessee |
E912730
|
entity |
| Predicate | distanceToGreatSmokyMountainsNationalParkMiles |
P44652
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Newport, Tennessee, distanceToGreatSmokyMountainsNationalParkMiles, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGreatSmokyMountainsNationalParkMiles Context triple: [Newport, Tennessee, distanceToGreatSmokyMountainsNationalParkMiles, 20]
-
A.
distanceToGreatSmokyMountainsNationalPark
chosen
Indicates the spatial distance between an entity and Great Smoky Mountains National Park.
-
B.
distanceToRockyMountMiles
Indicates the distance, measured in miles, between an entity and Rocky Mount.
-
C.
distanceToNashvilleInMilesApprox
Indicates the approximate distance, measured in miles, between a given entity’s location and Nashville.
-
D.
distanceToMountRainierNationalParkEntranceInMiles
Indicates the numerical distance, measured in miles, from a given location to the entrance of Mount Rainier National Park.
-
E.
distanceToKnoxville
Indicates the spatial distance between a given entity’s location and the city of Knoxville.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.