Triple
T26297085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Digital Editions |
E661445
|
entity |
| Predicate | supportsDevicesPerAccount |
P5992
|
FINISHED |
| Object | multiple devices |
—
|
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: multiple devices | Statement: [Adobe Digital Editions, supportsDevicesPerAccount, multiple devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDevicesPerAccount Context triple: [Adobe Digital Editions, supportsDevicesPerAccount, multiple devices]
-
A.
supportsDeviceCount
chosen
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
B.
supportsMultipleAppleIDsPerFamily
Indicates that the subject allows or is compatible with having more than one Apple ID associated with a single family group.
-
C.
maximumDevicesPerChannel
Indicates the highest number of devices that are allowed to be associated with or operate on a single channel.
-
D.
maximumDaisyChainedDevices
Indicates the maximum number of devices that can be connected in a daisy-chain configuration within the specified context.
-
E.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 26, 2026, 10:13 p.m.