Triple

T430924
Position Surface form Disambiguated ID Type / Status
Subject Immaculate Conception E9709 entity
Predicate reasonGiven P6484 FINISHED
Object fitting privilege in view of Mary’s role as Mother of God 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: fitting privilege in view of Mary’s role as Mother of God | Statement: [Immaculate Conception, reasonGiven, fitting privilege in view of Mary’s role as Mother of God]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonGiven
Context triple: [Immaculate Conception, reasonGiven, fitting privilege in view of Mary’s role as Mother of God]
  • A. reasonWritten
    Indicates that one entity is the reason or motivation for which another entity was written or authored.
  • B. originalReason chosen
    Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
  • C. selectionReason
    Indicates the reason or justification for choosing or selecting one entity over alternatives.
  • D. reasonForCreation
    Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
  • E. reasonForChange
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eeef065c81908ed30528a61da132 completed Feb. 28, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69a2edd9264c8190b92f9a50348e5541 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.