Triple

T3522566
Position Surface form Disambiguated ID Type / Status
Subject PCP theorem E74456 entity
Predicate verificationProperty P4965 FINISHED
Object verifier reads only a constant number of bits of the proof 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: verifier reads only a constant number of bits of the proof | Statement: [PCP theorem, verificationProperty, verifier reads only a constant number of bits of the proof]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: verificationProperty
Context triple: [PCP theorem, verificationProperty, verifier reads only a constant number of bits of the proof]
  • A. verificationStatus
    Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
  • B. confirmationMethod chosen
    Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
  • C. dataTypeVerified
    Indicates that the data’s type has been checked and confirmed to match the expected or required type.
  • D. requiresProofOf
    Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
  • E. confirmedBy
    Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
  • 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_69ad85d0c5488190a3d8e02ebd01a1aa completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc4dd6d48190a5a3f4b86c82b86c completed March 8, 2026, 6:13 p.m.
PD Predicate disambiguation batch_69adae121a048190b03825a001d21f49 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:19 p.m.