Triple

T3235650
Position Surface form Disambiguated ID Type / Status
Subject San Francisco National Cemetery E67847 entity
Predicate hasBurialEligibility P47508 FINISHED
Object eligible United States veterans and their dependents 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: eligible United States veterans and their dependents | Statement: [San Francisco National Cemetery, hasBurialEligibility, eligible United States veterans and their dependents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBurialEligibility
Context triple: [San Francisco National Cemetery, hasBurialEligibility, eligible United States veterans and their dependents]
  • A. burialStatus
    Indicates the state or condition of whether and how an entity has been buried.
  • B. hasBurialsFrom
    Indicates that a location or site contains burials originating from a specified time period, culture, or source.
  • C. hasTypeOfBurial
    Indicates the specific kind or method of burial associated with an entity.
  • D. burialBy
    Indicates that one entity is responsible for burying or interring another entity.
  • E. hasNotableBurials
    Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
  • 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_69ad858d27348190abb61c280b4c86a9 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaede0bdc8190a466f11bf2c50836 completed March 8, 2026, 5:16 p.m.
PD Predicate disambiguation batch_69ada4159e0481908cbbdd750f5e08c7 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada698eeb48190a1f5762fdd3b7b63 completed March 8, 2026, 4:40 p.m.
Created at: March 8, 2026, 3:08 p.m.