Triple
T27582915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino ACL |
E699625
|
entity |
| Predicate | supportsPrivilege |
P198958
|
FINISHED |
| Object | Create documents |
—
|
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: Create documents | Statement: [Domino ACL, supportsPrivilege, Create documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPrivilege Context triple: [Domino ACL, supportsPrivilege, Create documents]
-
A.
supportsPrivilegeLevels
Indicates that an entity is capable of handling or enforcing multiple distinct privilege or access levels within its operations or permissions system.
-
B.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
C.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
D.
requiresPrivileges
Indicates that performing the referenced action or accessing the referenced resource is contingent on the actor having specific privileges or permissions.
-
E.
supportedRight
Indicates that one entity endorsed, upheld, or actively backed the right or entitlement held by another entity.
- F. None of above. chosen
Provenance (4 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
| PDg | Predicate description generation | batch_69ff17bda59c8190b27c524f3e01c6df |
completed | May 9, 2026, 11:17 a.m. |
Created at: April 27, 2026, 2:03 p.m.