Triple
T27825902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nest Secure |
E702951
|
entity |
| Predicate | securityMode |
P11824
|
FINISHED |
| Object | home mode |
—
|
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: home mode | Statement: [Nest Secure, securityMode, home mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityMode Context triple: [Nest Secure, securityMode, home mode]
-
A.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
B.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
C.
securityParameter
Indicates a relationship where a specific parameter defines or configures the level or characteristics of security applied to an entity or process.
-
D.
securityStatus
chosen
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
E.
securityMechanisms
Indicates the protective methods, controls, or procedures implemented to safeguard entities from threats, vulnerabilities, or unauthorized actions.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 5:52 p.m.