Triple

T35760321
Position Surface form Disambiguated ID Type / Status
Subject CDC 6600 E1033552 entity
Predicate mainProcessorType P186412 FINISHED
Object central processor with hardwired control 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: central processor with hardwired control | Statement: [CDC 6600, mainProcessorType, central processor with hardwired control]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainProcessorType
Context triple: [CDC 6600, mainProcessorType, central processor with hardwired control]
  • A. mainProcessor
    Indicates that an entity serves as the primary or central processing unit responsible for executing core operations or computations for another entity or system.
  • B. primaryProcess
    Indicates that one process is the main or most fundamental process in relation to another process or within a given system or context.
  • C. processType
    Indicates the specific kind or category of process that an entity or activity belongs to.
  • D. builtInProcessor
    Indicates that one entity serves as an internal or integrated processing unit within another entity.
  • E. isProcessedBy
    Indicates that an entity undergoes some form of handling, transformation, or treatment performed by another entity or agent.
  • 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_69f76e1262f48190a313318665acc189 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7cec454a88190a9f3bbee2b856636 completed May 3, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69f7c8977c288190997a892ec5f756ed completed May 3, 2026, 10:13 p.m.
PDg Predicate description generation batch_69f7cec398ac819081c954a993c323ee completed May 3, 2026, 10:40 p.m.
Created at: May 3, 2026, 4:06 p.m.