Triple
T15989789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Figma |
E387792
|
entity |
| Predicate | supportsPermissionModel |
P83854
|
FINISHED |
| Object | file-level permissions |
—
|
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: file-level permissions | Statement: [Figma, supportsPermissionModel, file-level permissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPermissionModel Context triple: [Figma, supportsPermissionModel, file-level permissions]
-
A.
supportsPermissionType
chosen
Indicates that one entity is capable of handling, allowing, or being configured with a specified type of permission.
-
B.
supportsAccessModel
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
C.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
D.
definesPermissionState
Indicates that an entity specifies or establishes the current permission status or access rights applicable to another entity or action.
-
E.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.