Triple

T2166114
Position Surface form Disambiguated ID Type / Status
Subject Activation Lock E46911 entity
Predicate requiresForSetup P18895 FINISHED
Object previous owner’s Apple ID credentials when locked 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: previous owner’s Apple ID credentials when locked | Statement: [Activation Lock, requiresForSetup, previous owner’s Apple ID credentials when locked]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresForSetup
Context triple: [Activation Lock, requiresForSetup, previous owner’s Apple ID credentials when locked]
  • A. mayRequireComponent
    Indicates that one entity can optionally depend on or need another entity as a component for its proper use or operation.
  • B. requiresCapability
    Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
  • C. requiresPresence chosen
    Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
  • D. requiresSoftware
    Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
  • E. requiresPermitFor
    Indicates that one entity must obtain formal permission or authorization before performing an action involving 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_69a88a184cbc8190877791f6552c2484 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbeab223881908aaa2bc4f85329cc completed March 7, 2026, 5:59 a.m.
PD Predicate disambiguation batch_69abbd9c90408190b6b65498ca43ce26 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:45 p.m.