Triple

T10111630
Position Surface form Disambiguated ID Type / Status
Subject Articles of Faith E218252 entity
Predicate hasCanonicalStatusSince P42477 FINISHED
Object late 19th century 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: late 19th century | Statement: [Articles of Faith, hasCanonicalStatusSince, late 19th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCanonicalStatusSince
Context triple: [Articles of Faith, hasCanonicalStatusSince, late 19th century]
  • A. hasAdministrativeStatusSince
    Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
  • B. hasVersionStatus
    Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
  • C. canonicalStatus
    Indicates the formal or official standing of an entity within an established authoritative or normative system.
  • D. hasChronologyStatus
    Indicates the temporal or sequential status of something within a chronology, such as whether its position or order in time is known, uncertain, or otherwise classified.
  • E. hasHistorySince chosen
    Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
  • 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_69ca83da93fc8190b54e44bc2b34857c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd15d1fd081908c6f6b021e3999da completed April 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69cd4b9ed7e48190aa132ef8a69b49f9 completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:03 p.m.