Triple
T11401915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VA 7 |
E270128
|
entity |
| Predicate | hasControlledAccessSections |
P15393
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [VA 7, hasControlledAccessSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlledAccessSections Context triple: [VA 7, hasControlledAccessSections, yes]
-
A.
hasSecurityAccessControl
Indicates that an entity enforces or is associated with mechanisms that regulate and control access to resources or information for security purposes.
-
B.
controlsAccessBetween
Indicates that one entity regulates, manages, or restricts the ability of another entity to interact or communicate with a third entity or resource.
-
C.
controlsAccessTo
chosen
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
D.
hasAccessConstraint
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
-
E.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.