Triple

T4767831
Position Surface form Disambiguated ID Type / Status
Subject Visitation E105854 entity
Predicate traditionalWesternDateBefore1969 P31438 FINISHED
Object July 2 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: July 2 | Statement: [Visitation, traditionalWesternDateBefore1969, July 2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalWesternDateBefore1969
Context triple: [Visitation, traditionalWesternDateBefore1969, July 2]
  • A. traditionallyDated chosen
    Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
  • B. usesJulianCalendar
    Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
  • C. dateSecularized
    Indicates the date on which a religious or ecclesiastical entity was formally converted to secular (non-religious) status.
  • D. formerFixedDate
    Indicates that a previously established specific date associated with an event or relationship has changed and is no longer current.
  • E. dateDetermination
    Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:21 p.m.