Triple
T31027009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M-68K |
E790606
|
entity |
| Predicate | supportsCharacterDevices |
P207339
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CP/M-68K, supportsCharacterDevices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCharacterDevices Context triple: [CP/M-68K, supportsCharacterDevices, yes]
-
A.
characteristicDevice
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
B.
supportsDeviceTree
Indicates that one entity is compatible with and can operate using a device tree configuration provided by another entity.
-
C.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
D.
supportedByCharacter
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
-
E.
supportsDeviceProfiles
Indicates that one entity is capable of recognizing, handling, or operating with specified device configuration profiles.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:58 p.m.