Triple

T35818281
Position Surface form Disambiguated ID Type / Status
Subject Kodak, Tennessee E1035427 entity
Predicate nearTouristCorridor P144533 FINISHED
Object gateway to Sevier County tourist destinations 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: gateway to Sevier County tourist destinations | Statement: [Kodak, Tennessee, nearTouristCorridor, gateway to Sevier County tourist destinations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearTouristCorridor
Context triple: [Kodak, Tennessee, nearTouristCorridor, gateway to Sevier County tourist destinations]
  • A. nearestTouristDestination
    Indicates that one location is the closest tourist destination to another specified location.
  • B. tourismCorridor chosen
    Indicates a designated route or area that links multiple destinations to facilitate and promote tourism-related movement and activities between them.
  • C. typicalNearbyLandmarks
    Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
  • D. nearbyTo
    Indicates that one entity is located close in distance or position to another entity.
  • E. nearScenicRoute
    Indicates that one entity is located close to a route or path that is considered scenic or visually appealing.
  • 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_69f76e185ffc8190880b3cdf51decd38 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8d219f8819081dc4ce3c83ca0cb completed May 3, 2026, 7:58 p.m.
Created at: May 3, 2026, 4:06 p.m.