Triple
T2166109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Activation Lock |
E46911
|
entity |
| Predicate | statusCanBeCheckedBy |
P3257
|
FINISHED |
| Object | MDM solutions in organizations |
—
|
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: MDM solutions in organizations | Statement: [Activation Lock, statusCanBeCheckedBy, MDM solutions in organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCanBeCheckedBy Context triple: [Activation Lock, statusCanBeCheckedBy, MDM solutions in organizations]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
checkedBy
chosen
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
C.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
D.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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.