Triple

T33353470
Position Surface form Disambiguated ID Type / Status
Subject downtown Mechanicsburg historic district E854006 entity
Predicate hasFunctionInCommunity P108949 FINISHED
Object focus of local businesses 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: focus of local businesses | Statement: [downtown Mechanicsburg historic district, hasFunctionInCommunity, focus of local businesses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFunctionInCommunity
Context triple: [downtown Mechanicsburg historic district, hasFunctionInCommunity, focus of local businesses]
  • A. hasCommunityFunction chosen
    Indicates that an entity serves or provides a function, role, or service that benefits or supports a community.
  • B. hasCommunityIn
    Indicates that a community is present, active, or established within a specified location, platform, or context.
  • C. hasCommunitySupport
    Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
  • D. hadFunction
    Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
  • E. hasCommunityResource
    Indicates that an entity provides, contains, or is associated with a resource intended for use by a community.
  • 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_69f3496acbc8819099fd0305ecc42080 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:34 a.m.