Triple

T2969707
Position Surface form Disambiguated ID Type / Status
Subject Papacy E80250 entity
Predicate heldTemporalPowerUntil P29191 FINISHED
Object 1870 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: 1870 | Statement: [Papacy, heldTemporalPowerUntil, 1870]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldTemporalPowerUntil
Context triple: [Papacy, heldTemporalPowerUntil, 1870]
  • A. heldTemporalPower chosen
    Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
  • B. heldTitleUntil
    Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
  • C. heldAfter
    Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
  • D. heldOn
    Indicates that an event or activity takes place at a specific time, date, or occasion.
  • E. holdsOver
    Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
  • 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_69ad8b14ffe881908ffed62f9595c867 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad997282b481909d078be0e70d9930 completed March 8, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69ad960e71f8819088179d11248c6ed0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.