Triple
T30422526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPEs |
E773936
|
entity |
| Predicate | cannotDirectlyAccess |
P13175
|
FINISHED |
| Object | system memory |
—
|
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: system memory | Statement: [SPEs, cannotDirectlyAccess, system memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotDirectlyAccess Context triple: [SPEs, cannotDirectlyAccess, system memory]
-
A.
notAccessibleBy
chosen
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
B.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
C.
hasNoAccess
Indicates that an entity is denied or lacks permission to access another entity, resource, or location.
-
D.
notConstructibleDirectly
Indicates that the entity cannot be instantiated or created directly, typically requiring an alternative or indirect construction method.
-
E.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:06 p.m.