Triple

T34124906
Position Surface form Disambiguated ID Type / Status
Subject South Whitley, Indiana E875246 entity
Predicate hasCommunityDescription P205331 FINISHED
Object small Midwestern town 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: small Midwestern town | Statement: [South Whitley, Indiana, hasCommunityDescription, small Midwestern town]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommunityDescription
Context triple: [South Whitley, Indiana, hasCommunityDescription, small Midwestern town]
  • A. hasCommunityIn
    Indicates that a community is present, active, or established within a specified location, platform, or context.
  • B. hasCommunityGroup
    Indicates that an entity is associated with, or belongs to, a specific community group.
  • C. hasCommunityContext
    Indicates that something exists or occurs within, or is influenced by, a particular community’s social, cultural, or environmental context.
  • D. hasCommunitySupport
    Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
  • E. hasCommunityMedia
    Indicates that an entity possesses, operates, or is associated with media outlets or channels that are created for and/or by a specific community.
  • F. None of above. chosen

Provenance (4 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_69f349aa33848190a2e6c5e4533c8444 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c92f03c8190ae2751270b195423 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379f963908190846d232f386fd98f completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c80ba448190853011097a151b7e completed May 12, 2026, 7:16 p.m.
Created at: May 1, 2026, 1:53 a.m.