Triple
T25931976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enclave Page Cache |
E653457
|
entity |
| Predicate | limitedResource |
P160305
|
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: [Enclave Page Cache, limitedResource, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedResource Context triple: [Enclave Page Cache, limitedResource, yes]
-
A.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
B.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
C.
limitedMembershipTo
Indicates that access, participation, or inclusion in something is restricted to a specific subset of entities or members.
-
D.
limitedInstitution
Indicates that an institution has restricted scope, authority, or operational capacity within a broader system or context.
-
E.
limitedSystemType
Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f604192b6c8190b86e151a628eafd8 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 8:37 a.m.