Triple
T7279120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel SGX |
E163103
|
entity |
| Predicate | attestationType |
P22964
|
FINISHED |
| Object | Local attestation |
—
|
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: Local attestation | Statement: [Intel SGX, attestationType, Local attestation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attestationType Context triple: [Intel SGX, attestationType, Local attestation]
-
A.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
-
B.
hasAttestation
chosen
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
C.
degreeOfAttestation
Indicates the extent or level to which something (such as a claim, form, or document) is supported, verified, or confirmed by evidence or authoritative sources.
-
D.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
E.
certificateType
Indicates the specific kind or category of certificate associated with an entity or relationship.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.