Triple

T14268309
Position Surface form Disambiguated ID Type / Status
Subject UltraSPARC T2 E353708 entity
Predicate supportsOnChipNetworking P113511 FINISHED
Object yes 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: yes | Statement: [UltraSPARC T2, supportsOnChipNetworking, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOnChipNetworking
Context triple: [UltraSPARC T2, supportsOnChipNetworking, yes]
  • A. supportsNetworkingModel
    Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
  • B. requiresSupportChips
    Indicates that an entity depends on or needs additional support components (chips) in order to function or be used properly.
  • C. hasCellularComponent
    Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
  • D. supportsTethering
    Indicates that one entity enables or allows another entity to share its network connection with additional devices (i.e., provides tethering capability).
  • E. supportedNetwork
    Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6358c2288190ac1fd26e688a605d completed April 14, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69de2a7d586c8190846ff242bbf5ac53 completed April 14, 2026, 11:52 a.m.
PDg Predicate description generation batch_69de2e07d1f88190bdcd20967e484718 completed April 14, 2026, 12:07 p.m.
Created at: April 10, 2026, 1:10 a.m.