Triple

T36359383
Position Surface form Disambiguated ID Type / Status
Subject Cold Fusion E895444 entity
Predicate hardwareCategoryOfProduct P76305 FINISHED
Object consumer desktop computer 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: consumer desktop computer | Statement: [Cold Fusion, hardwareCategoryOfProduct, consumer desktop computer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hardwareCategoryOfProduct
Context triple: [Cold Fusion, hardwareCategoryOfProduct, consumer desktop computer]
  • A. hardwareCategory chosen
    Indicates that an item belongs to or is classified under a specific hardware category or type.
  • B. hardwareUsedBy
    Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
  • C. hardwareUsed
    Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
  • D. hardwareComponent
    Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
  • E. componentCategory
    Indicates that one entity is classified as belonging to a particular component category of another entity.
  • 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_69f76e5044248190b390d8887dc03254 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb3ff1b08190802b1063d55d3923 completed May 3, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69f7b9a611a081908dd6aec1df3f4d7f completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.