Triple
T2166112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Activation Lock |
E46911
|
entity |
| Predicate | persistsAfter |
P36117
|
FINISHED |
| Object | device erase |
—
|
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: device erase | Statement: [Activation Lock, persistsAfter, device erase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persistsAfter Context triple: [Activation Lock, persistsAfter, device erase]
-
A.
persistence
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
-
B.
supportsPersistence
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
C.
permanence
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
D.
perpetuates
Indicates that one entity causes a state, condition, or situation involving another entity to continue or persist over time.
-
E.
preservesAsTimeOf
Indicates that one entity maintains or records another entity specifically as a temporal reference or time-related designation.
- 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_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. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.