Triple

T32255040
Position Surface form Disambiguated ID Type / Status
Subject Lanesville, Indiana E823991 entity
Predicate heritageFestivalTheme P7933 FINISHED
Object local history 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: local history | Statement: [Lanesville, Indiana, heritageFestivalTheme, local history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritageFestivalTheme
Context triple: [Lanesville, Indiana, heritageFestivalTheme, local history]
  • A. heritageTheme chosen
    Indicates that something is associated with, represents, or is categorized under a particular cultural or historical heritage theme.
  • B. heritageFestivalOccursIn
    Indicates that a heritage festival takes place or is held within a specific location or area.
  • C. culturalThemes
    Indicates that there is a relationship between entities where one embodies, expresses, or is associated with particular cultural themes present in or derived from the other.
  • D. hasFestivalTheme
    Indicates that something is associated with, characterized by, or designed around a particular festival-related theme.
  • E. heritageTradition
    Indicates a relationship where a cultural practice, belief, or custom is passed down and maintained as part of a group’s inherited traditions.
  • 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_69f3490db0748190bfef6e50c95d39d3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: May 1, 2026, 12:41 a.m.