Triple

T14422348
Position Surface form Disambiguated ID Type / Status
Subject PlayStation 4 system software browser E357613 entity
Predicate cannotBeUninstalled P114205 FINISHED
Object true 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: true | Statement: [PlayStation 4 system software browser, cannotBeUninstalled, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cannotBeUninstalled
Context triple: [PlayStation 4 system software browser, cannotBeUninstalled, true]
  • A. cannotBeRemovedBy
    Indicates that one entity is not capable of removing, deleting, or otherwise eliminating another entity.
  • B. cannotBeEasilyDisabled
    Indicates that the relationship or mechanism cannot be turned off, bypassed, or neutralized without significant effort, expertise, or resources.
  • C. cannotBeUsedWithout
    Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
  • D. neverActuallyInstalled
    Indicates that an entity was planned or referenced for installation but was ultimately never installed or put into effect.
  • E. canBeRemovedBy
    Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91102c3c81908f571a1fff3bdd47 completed April 14, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69de5c30467881908e770e3940295641 completed April 14, 2026, 3:24 p.m.
PDg Predicate description generation batch_69de5fb4de14819092acdecbd201d672 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:18 a.m.