Triple

T4468011
Position Surface form Disambiguated ID Type / Status
Subject Laetentur Caeli E98425 entity
Predicate laterReceptionInEast P9563 FINISHED
Object largely rejected in Eastern Orthodox world 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: largely rejected in Eastern Orthodox world | Statement: [Laetentur Caeli, laterReceptionInEast, largely rejected in Eastern Orthodox world]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterReceptionInEast
Context triple: [Laetentur Caeli, laterReceptionInEast, largely rejected in Eastern Orthodox world]
  • A. laterReception chosen
    Indicates that one entity receives or accepts something at a time that is later than when another related reception or event occurs.
  • B. laterLocation
    Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
  • C. locationOfLaterMeeting
    Indicates the place where a subsequent or future meeting is scheduled or expected to occur.
  • D. reception
    Indicates the act of receiving or welcoming someone or something, often marking the initial acknowledgment or acceptance in an interaction or process.
  • E. laterSought
    Indicates that one entity attempted to obtain, pursue, or request another entity at a subsequent time relative to some prior reference point.
  • 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_69b3454b4ae481908967426dd37284d6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356fb69a0819099f0005779f4fcac completed March 13, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69b3563bf4f8819081726cde3a34460b completed March 13, 2026, 12:11 a.m.
Created at: March 12, 2026, 11:34 p.m.