Triple
T9499060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARMv8-A |
E229087
|
entity |
| Predicate | definesExceptionLevel |
P88958
|
FINISHED |
| Object | EL0 |
—
|
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: EL0 | Statement: [ARMv8-A, definesExceptionLevel, EL0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesExceptionLevel Context triple: [ARMv8-A, definesExceptionLevel, EL0]
-
A.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
B.
doctrineLevel
Indicates the degree or intensity to which a doctrine, teaching, or set of principles is held, emphasized, or applied in a given context.
-
C.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
exception
Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
-
E.
coversLevel
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983a94c48190a7ddf95a953c4ecc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.