Triple
T10329346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permissions API |
E242836
|
entity |
| Predicate | permissionStateValuesInclude |
P93440
|
FINISHED |
| Object | granted |
—
|
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: granted | Statement: [Permissions API, permissionStateValuesInclude, granted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permissionStateValuesInclude Context triple: [Permissions API, permissionStateValuesInclude, granted]
-
A.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
B.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
C.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
D.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
E.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.