Triple
T28525519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M-Plus |
E721893
|
entity |
| Predicate | supportedCPU |
P202869
|
FINISHED |
| Object | Intel 8080 |
—
|
NE NERFINISHED |
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: Intel 8080 | Statement: [CP/M-Plus, supportedCPU, Intel 8080]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedCPU Context triple: [CP/M-Plus, supportedCPU, Intel 8080]
-
A.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
B.
supportsIntel64
Indicates that one entity provides compatibility with or operational support for Intel 64-bit (x86-64) architecture in relation to another entity.
-
C.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
-
D.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
| PDg | Predicate description generation | batch_6a00c9dd1eac8190b33c620ddfae7981 |
completed | May 10, 2026, 6:09 p.m. |
Created at: April 28, 2026, 3:24 a.m.