Triple
T25436464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CISC |
E637384
|
entity |
| Predicate | oftenImplements |
P127762
|
FINISHED |
| Object | instructions via microcode |
—
|
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: instructions via microcode | Statement: [CISC, oftenImplements, instructions via microcode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenImplements Context triple: [CISC, oftenImplements, instructions via microcode]
-
A.
alsoImplements
Indicates that an entity, in addition to its primary implementation, implements another interface, protocol, or specification as well.
-
B.
isOftenImplementedAs
chosen
Indicates that one thing is frequently realized, instantiated, or carried out in the form of another.
-
C.
usesImplement
Indicates that one entity employs or makes use of another entity as a tool, instrument, or means to perform an action or achieve a purpose.
-
D.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
E.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements of, another entity.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:59 p.m.