Triple
T14086504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIS+ |
E339009
|
entity |
| Predicate | accessControlUnit |
P15393
|
FINISHED |
| Object | NIS+ rights mask |
—
|
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: NIS+ rights mask | Statement: [NIS+, accessControlUnit, NIS+ rights mask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessControlUnit Context triple: [NIS+, accessControlUnit, NIS+ rights mask]
-
A.
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.
-
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.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
securityAccess
Indicates that one entity has permission, authorization, or the ability to access or interact with another entity in a security-controlled context.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5edff1b881909ea56dc2429ef2dd |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.