Triple
T3863610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Knoxville |
E91797
|
entity |
| Predicate | directionRelativeToCityCenter |
P28261
|
FINISHED |
| Object | east of downtown Knoxville |
—
|
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: east of downtown Knoxville | Statement: [East Knoxville, directionRelativeToCityCenter, east of downtown Knoxville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionRelativeToCityCenter Context triple: [East Knoxville, directionRelativeToCityCenter, east of downtown Knoxville]
-
A.
directionFromCityCenter
chosen
Indicates the compass direction in which one location lies relative to the city center.
-
B.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
C.
geographicDirectionWithinCountry
Indicates that one place lies in a specified cardinal or intercardinal direction relative to another place within the same country.
-
D.
directionFromParis
Indicates the cardinal or relative compass direction of an entity as measured from Paris toward that entity.
-
E.
relativeLocationToCentralPark
Indicates the spatial position or orientation of an entity in relation to Central Park.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3871d881909c6c8e6d08203801 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.