Triple

T2268383
Position Surface form Disambiguated ID Type / Status
Subject Madison County, Kentucky E50600 entity
Predicate hasSignificantHeritage P10915 FINISHED
Object Civil War 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: Civil War history | Statement: [Madison County, Kentucky, hasSignificantHeritage, Civil War history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificantHeritage
Context triple: [Madison County, Kentucky, hasSignificantHeritage, Civil War history]
  • A. hasHistoricalSignificance
    Indicates that something possesses notable importance or influence within a historical context or period.
  • B. heritageValue chosen
    Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
  • C. hasHeritage
    Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
  • D. hasCulturalSignificance
    Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
  • E. hasArchitecturalSignificance
    Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
  • 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_69a88b05910c8190a9a2b1ff230c85f9 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc2ea65288190bc8644a07a11dfa9 completed March 7, 2026, 6:17 a.m.
PD Predicate disambiguation batch_69abbdb592588190ac1ef5e8c54575b1 completed March 7, 2026, 5:55 a.m.
Created at: March 4, 2026, 7:48 p.m.