Triple

T9422388
Position Surface form Disambiguated ID Type / Status
Subject Pashons E227184 entity
Predicate eraAlignment P88787 FINISHED
Object follows Coptic leap-year rules 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: follows Coptic leap-year rules | Statement: [Pashons, eraAlignment, follows Coptic leap-year rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eraAlignment
Context triple: [Pashons, eraAlignment, follows Coptic leap-year rules]
  • A. alignedAgainst
    Indicates that two or more entities are united in opposition to a common target, side, or objective.
  • B. forceAlignment
    Indicates that one entity compels another entity to match or conform its alignment, orientation, or position to its own or to a specified standard.
  • C. basedOnAlignmentOf
    Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
  • D. successorAlignment
    Indicates that one entity’s alignment, orientation, or configuration directly follows and is determined by that of another entity in a sequence or progression.
  • E. typicalAlignment
    Indicates the usual or most common way in which two entities are positioned, oriented, or arranged relative to each other.
  • F. None of above. chosen

Provenance (4 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_69ca8436ba308190903e470776d2d893 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd6c27c8cc8190a11162c10c33b17e completed April 1, 2026, 7:04 p.m.
PD Predicate disambiguation batch_69cca550777c819094e1851a6127cbbc completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca89b3368819087a3d69270c1f185 completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:48 p.m.