Triple

T27963521
Position Surface form Disambiguated ID Type / Status
Subject Apollos E704651 entity
Predicate scripturalSkill P60374 FINISHED
Object mighty in the Scriptures 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: mighty in the Scriptures | Statement: [Apollos, scripturalSkill, mighty in the Scriptures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scripturalSkill
Context triple: [Apollos, scripturalSkill, mighty in the Scriptures]
  • A. scripturalExpertise chosen
    Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
  • B. scripturalFunction
    Indicates the role or purpose that a text or passage serves within a scriptural or religious context.
  • C. scripturalFeature
    Indicates a relationship where something possesses or exhibits a characteristic, element, or quality specifically associated with scripture or sacred texts.
  • D. scriptureFor
    Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
  • E. hasScripture
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • 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_69ef841061e48190b5570f9562f7434d completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6978fe97081908fe568091ad9b159 completed May 3, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
Created at: April 27, 2026, 7:33 p.m.