Triple

T27727980
Position Surface form Disambiguated ID Type / Status
Subject stoning of Paul E697352 entity
Predicate hasOutcomeForPaul P59870 FINISHED
Object continued preaching of the gospel 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: continued preaching of the gospel | Statement: [stoning of Paul, hasOutcomeForPaul, continued preaching of the gospel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOutcomeForPaul
Context triple: [stoning of Paul, hasOutcomeForPaul, continued preaching of the gospel]
  • A. outcomeOf chosen
    Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
  • B. hasOutcomeDeterminedBy
    Indicates that the result or consequence of one entity is decided, controlled, or directly influenced by another entity.
  • C. hasOutcomeForPirithous
    Indicates that an action, event, or decision results in a specific consequence or effect for Pirithous.
  • D. hasConclusion
    Indicates that something leads to, results in, or is associated with a particular conclusion.
  • E. hasProposedOutcome
    Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f67c9fe7b48190b79b4041357edb49 completed May 2, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69f678cc272081909e5c70f1bc7407f0 completed May 2, 2026, 10:21 p.m.
Created at: April 27, 2026, 3:10 p.m.