Triple

T6560479
Position Surface form Disambiguated ID Type / Status
Subject Petrolia, California E152569 entity
Predicate hasVolunteerService P5502 FINISHED
Object volunteer fire department 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: volunteer fire department | Statement: [Petrolia, California, hasVolunteerService, volunteer fire department]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVolunteerService
Context triple: [Petrolia, California, hasVolunteerService, volunteer fire department]
  • A. volunteeredFor
    Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
  • B. hasVolunteerStatus
    Indicates that an entity holds a particular volunteer-related status or role within a specified context.
  • C. hasVolunteerProgram
    Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
  • D. hasVolunteerBase chosen
    Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
  • E. hasCommunityServed
    Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
  • 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_69c688058d6881908c19b309cc55dbfa completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6c1b15d3481908ae66e3d7564b352 completed March 27, 2026, 5:43 p.m.
PD Predicate disambiguation batch_69c6acf6d4148190914b19e9affd8c76 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:52 p.m.