Triple
T29343168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CompuPro |
E744090
|
entity |
| Predicate | supportedOperatingSystems |
P13398
|
FINISHED |
| Object | CP/M |
E40551
|
NE 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: CP/M | Statement: [CompuPro, supportedOperatingSystems, CP/M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedOperatingSystems Context triple: [CompuPro, supportedOperatingSystems, CP/M]
-
A.
supportedSystem
chosen
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
B.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
C.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
D.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
E.
relatedOperatingSystem
Indicates that there is an association between an entity and an operating system that is relevant to its use, compatibility, or operation.
- F. None of above.
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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a262d48ed7c8190a11a4c7bd47a34c4 |
completed | June 8, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
Created at: April 28, 2026, 1:34 p.m.