Triple

T19131687
Position Surface form Disambiguated ID Type / Status
Subject Created for Community E468329 entity
Predicate connectsConcept P531 FINISHED
Object doctrine of the Trinity and human community 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: doctrine of the Trinity and human community | Statement: [Created for Community, connectsConcept, doctrine of the Trinity and human community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsConcept
Context triple: [Created for Community, connectsConcept, doctrine of the Trinity and human community]
  • A. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • B. connectsWorks
    Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
  • C. connectsPartOf
    Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
  • D. exportsConcept
    Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
  • E. hasConcept chosen
    Indicates that an entity includes, embodies, or is associated with a particular concept.
  • 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_69d8dd0796a48190b34ce4cd9d3f3be5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e3e980288190859026c0a0873fe2 completed April 20, 2026, 8:29 a.m.
PD Predicate disambiguation batch_69e4b9b085288190b974d649e12e0844 completed April 19, 2026, 11:17 a.m.
Created at: April 10, 2026, 12:05 p.m.