Triple

T26966683
Position Surface form Disambiguated ID Type / Status
Subject BPP E679189 entity
Predicate typicalResource P199363 FINISHED
Object polynomial number of random bits 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: polynomial number of random bits | Statement: [BPP, typicalResource, polynomial number of random bits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalResource
Context triple: [BPP, typicalResource, polynomial number of random bits]
  • A. primaryResourceType
    Indicates the main or predominant type/category of resource associated with an entity or activity.
  • B. traditionalResource
    Indicates that one entity is a resource or practice that has been passed down through tradition and is recognized as part of a longstanding cultural or customary system used by another entity.
  • C. typicalItem
    Indicates that an item is a representative or characteristic example of a broader category, class, or set.
  • D. coveredResource
    Indicates that one entity serves as a resource that is included within the scope or protection of another entity (such as a policy, agreement, or coverage).
  • E. typicalCoreType
    Indicates that something is a standard or characteristic core type within a given classification or system.
  • 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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69ff32b88bf48190b45afd1b60cb511c completed May 9, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69ff3031e18881908927b2ab452de863 completed May 9, 2026, 1:01 p.m.
PDg Predicate description generation batch_69ff32b6dd448190a7a6ebb76b99d4cc completed May 9, 2026, 1:12 p.m.
Created at: April 27, 2026, 6:36 a.m.