Triple
T32013554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL10 |
E817471
|
entity |
| Predicate | supportsMultiUser |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultiUser Context triple: [KL10, supportsMultiUser, yes]
-
A.
supportsMultiuser
chosen
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
B.
supportsCheckUsers
Indicates that an entity is capable of performing or enabling user verification or user status checks for another entity.
-
C.
supportsSeparateAccounts
Indicates that one entity enables or allows the use or management of distinct, individually maintained accounts rather than a single shared account.
-
D.
supportsUserServices
Indicates that one entity provides the necessary functionality or resources for user-facing services to operate or be delivered.
-
E.
supportsUsers
Indicates that one entity provides assistance, functionality, or compatibility for the users associated with another entity.
- F. None of above.
Provenance (1 batch)
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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:15 a.m.