Triple
T33434761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamepad API |
E856214
|
entity |
| Predicate | securityModelIncludes |
P188911
|
FINISHED |
| Object | same-origin policy |
—
|
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: same-origin policy | Statement: [Gamepad API, securityModelIncludes, same-origin policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityModelIncludes Context triple: [Gamepad API, securityModelIncludes, same-origin policy]
-
A.
securityModelIdentifier
Indicates the specific security model or framework under which an entity, interaction, or policy is defined or governed.
-
B.
securityModelAbbreviation
Indicates that one entity is the standard or commonly used abbreviated form of the name or identifier of a particular security model.
-
C.
securityModelSimilarTo
Indicates that one entity’s security model is similar or comparable to that of another entity.
-
D.
securityPracticeIncludes
Indicates that a broader security practice encompasses, contains, or makes use of a specific security measure, control, or activity.
-
E.
securityLevelsInclude
Indicates that one entity’s defined security levels contain or encompass the security levels of 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:36 a.m.