Triple

T6340287
Position Surface form Disambiguated ID Type / Status
Subject Council of Rome (382) E142606 entity
Predicate recognizedAsCanonical P310 FINISHED
Object four Gospels 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: four Gospels | Statement: [Council of Rome (382), recognizedAsCanonical, four Gospels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAsCanonical
Context triple: [Council of Rome (382), recognizedAsCanonical, four Gospels]
  • A. recognizedAs chosen
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
  • B. recognizedFor
    Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
  • C. recognizedAsDomain
    Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
  • D. recognizedIn
    Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
  • E. hasCanonization
    Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
  • 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_69c008d5ab108190b346c465696824a9 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0674311388190bb069a07a7ff60ef completed March 22, 2026, 10:03 p.m.
PD Predicate disambiguation batch_69c060ea1a988190889e47b7e0c819b8 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:30 p.m.