Triple

T6274841
Position Surface form Disambiguated ID Type / Status
Subject Effingham County E140629 entity
Predicate hasHistoricCommunities P11485 FINISHED
Object historic communities 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: historic communities | Statement: [Effingham County, hasHistoricCommunities, historic communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricCommunities
Context triple: [Effingham County, hasHistoricCommunities, historic communities]
  • A. hasHistoricCommunity chosen
    Indicates that an entity is associated with, contains, or is part of a community of historical significance.
  • B. hasCommunityIn
    Indicates that a community is present, active, or established within a specified location, platform, or context.
  • C. hasTraditionalCommunity
    Indicates that an entity possesses or is associated with a community that maintains traditional practices, customs, or ways of life.
  • D. hasApproximateNumberOfCommunitiesCommemorated
    Indicates that an entity is associated with an estimated or non-exact count of communities that are commemorated in relation to it.
  • E. hasHistoricCity
    Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
  • 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_69c008cc158881908df6ec94a911c736 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063c0629c8190805ddf1a604e9ca4 completed March 22, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69c05606fb50819082d1a5a91e5030b6 completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:25 p.m.