Triple
T3011193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston, Tennessee |
E82223
|
entity |
| Predicate | geographicDirectionWithinState |
P44650
|
FINISHED |
| Object | eastern Tennessee |
—
|
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: eastern Tennessee | Statement: [Kingston, Tennessee, geographicDirectionWithinState, eastern Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionWithinState Context triple: [Kingston, Tennessee, geographicDirectionWithinState, eastern Tennessee]
-
A.
nearbyState
Indicates that one state is geographically adjacent to or in close proximity to another state.
-
B.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
-
C.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
nearByCityState
Indicates that a city is geographically close to or within the same general area as a specified state.
- F. None of above. chosen
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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4e2c8c8190a8fed3604780826b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.