Triple

T7202371
Position Surface form Disambiguated ID Type / Status
Subject Third Order of the Society of Saint Pius X E148577 entity
Predicate hasVowsOrPromises P23834 FINISHED
Object promises of fidelity to the rule 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: promises of fidelity to the rule | Statement: [Third Order of the Society of Saint Pius X, hasVowsOrPromises, promises of fidelity to the rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVowsOrPromises
Context triple: [Third Order of the Society of Saint Pius X, hasVowsOrPromises, promises of fidelity to the rule]
  • A. hasTypeOfVows
    Indicates that one entity is characterized by or associated with a particular kind or category of vows.
  • B. vowsTo
    Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
  • C. promises
    Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
  • D. hasVow chosen
    Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
  • E. hasHook
    Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
  • 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e94a9ee4819086de79fcdfa1836a completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:52 p.m.