Triple

T14388400
Position Surface form Disambiguated ID Type / Status
Subject Tensor SoC family E356780 entity
Predicate securitySubsystem P2368 FINISHED
Object Titan M-based technology 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: Titan M-based technology | Statement: [Tensor SoC family, securitySubsystem, Titan M-based technology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securitySubsystem
Context triple: [Tensor SoC family, securitySubsystem, Titan M-based technology]
  • A. securityApparatusControl
    Indicates that one entity exercises authority over, manages, or directs the operations and decisions of a security or law-enforcement apparatus.
  • B. securityApparatusRole
    Indicates the role or function an entity holds within a security or law-enforcement apparatus.
  • C. securityEnvironment
    Indicates the overall conditions, threats, and protective measures that characterize the safety and risk context in which an entity operates.
  • D. securityFeature chosen
    Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
  • E. securityAccess
    Indicates that one entity has permission, authorization, or the ability to access or interact with another entity in a security-controlled context.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de90283b9c8190b50d30ad58bfe085 completed April 14, 2026, 7:06 p.m.
PD Predicate disambiguation batch_69de2aa024c48190805df6a9d63deb10 completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:16 a.m.