Triple

T7248919
Position Surface form Disambiguated ID Type / Status
Subject Network Computing Devices E156544 entity
Predicate competitorInConcept P1375 FINISHED
Object Sun Microsystems thin clients 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: Sun Microsystems thin clients | Statement: [Network Computing Devices, competitorInConcept, Sun Microsystems thin clients]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competitorInConcept
Context triple: [Network Computing Devices, competitorInConcept, Sun Microsystems thin clients]
  • A. competesWith chosen
    Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
  • B. competitionFrom
    Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
  • C. rivalOf
    Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
  • D. competitionOf
    Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
  • E. isCompetitive
    Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
  • 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_69c68827b5e481908dc05e145b2c92d4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea763f208190af1210cd8d2a05c9 completed March 27, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69c6e7666ffc81908bf643d8257e6337 completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:56 p.m.