Triple

T17723944
Position Surface form Disambiguated ID Type / Status
Subject Bethany Hamilton E442410 entity
Predicate hasReligiousThemeInWork P24743 FINISHED
Object Christian faith 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: Christian faith | Statement: [Bethany Hamilton, hasReligiousThemeInWork, Christian faith]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReligiousThemeInWork
Context triple: [Bethany Hamilton, hasReligiousThemeInWork, Christian faith]
  • A. hasReligiousTheme chosen
    Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
  • B. religionRelatedWork
    Indicates that a work (such as a text, artwork, or project) is related to, concerned with, or produced in the context of a particular religion or religious tradition.
  • C. hasReligiousCharacter
    Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
  • D. hasReligiousType
    Indicates that an entity is associated with or classified under a particular religion or religious category.
  • E. hasReligiousSee
    Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
  • 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4748900608190bf5ba04415edaffc completed April 19, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69e3cde815e08190881972e2d80d151e completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:07 a.m.