Triple
T7279128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel SGX |
E163103
|
entity |
| Predicate | memoryRegionAbbreviation |
P27729
|
FINISHED |
| Object | EPC |
—
|
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: EPC | Statement: [Intel SGX, memoryRegionAbbreviation, EPC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryRegionAbbreviation Context triple: [Intel SGX, memoryRegionAbbreviation, EPC]
-
A.
hasAbbreviationForRegion
chosen
Indicates that one entity is used as the standard abbreviated form of the name of a particular region.
-
B.
regulatorAbbreviation
Indicates that one entity is an abbreviation or shortened form of the name of a regulatory body or regulator associated with another entity.
-
C.
terminusRegion
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
D.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
E.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
- 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.