Triple

T25705795
Position Surface form Disambiguated ID Type / Status
Subject Longinus E644583 entity
Predicate survivingWorkStatus P75578 FINISHED
Object partially preserved 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: partially preserved | Statement: [Longinus, survivingWorkStatus, partially preserved]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: survivingWorkStatus
Context triple: [Longinus, survivingWorkStatus, partially preserved]
  • A. survivingWorkForm
    Indicates that one work is a surviving or extant form/version of another, typically when the original or earlier form is lost or no longer available.
  • B. hasSurvivalStatus
    Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
  • C. extentOfSurvivalOfWork chosen
    Indicates the degree to which a work has been preserved or remains extant.
  • D. hasWorkStatus
    Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
  • E. survivingFrom
    Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
  • 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_69e77e83c8ec8190bf52fcdac4838984 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fc113b40819088a0d53c824097e4 completed May 2, 2026, 1:28 p.m.
PD Predicate disambiguation batch_69f480824a1c81908a8a492eedbc2596 completed May 1, 2026, 10:29 a.m.
Created at: April 21, 2026, 9:04 p.m.