Triple
T7936055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EISA |
E184290
|
entity |
| Predicate | busWidthComparedToISA |
P79886
|
FINISHED |
| Object | wider than ISA |
—
|
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: wider than ISA | Statement: [EISA, busWidthComparedToISA, wider than ISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busWidthComparedToISA Context triple: [EISA, busWidthComparedToISA, wider than ISA]
-
A.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
B.
hasBaseISA
Indicates that an entity’s base or fundamental type is a specified ISA (Instruction Set Architecture) or foundational classification.
-
C.
memoryBandwidth
Indicates the rate at which data can be transferred to or from a memory system over a given period of time.
-
D.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
E.
supportsNumberOfChannelsOnTypicalMotherboard
Indicates that an entity accommodates or is compatible with the typical number of channels provided on a standard motherboard.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.