Triple
T33316997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airplane Mode |
E853039
|
entity |
| Predicate | doesNotDisable |
P127946
|
FINISHED |
| Object | local device storage |
—
|
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: local device storage | Statement: [Airplane Mode, doesNotDisable, local device storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotDisable Context triple: [Airplane Mode, doesNotDisable, local device storage]
-
A.
doesNotPrevent
chosen
Indicates that one entity or condition fails to stop, block, or inhibit another event, action, or state from occurring.
-
B.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
doesNotPreempt
Indicates that one action, event, or rule does not take priority over, override, or occur in place of another.
-
E.
doesNotBan
Indicates that one entity allows or permits another entity or action by explicitly not prohibiting it.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:33 a.m.