Triple
T28525545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M-Plus |
E721893
|
entity |
| Predicate | supportsFileSystemFeature |
P203
|
FINISHED |
| Object | file attributes |
—
|
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: file attributes | Statement: [CP/M-Plus, supportsFileSystemFeature, file attributes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFileSystemFeature Context triple: [CP/M-Plus, supportsFileSystemFeature, file attributes]
-
A.
fileSystemSupport
Indicates that one entity (such as a system, application, or device) is capable of recognizing, accessing, and correctly operating with a particular file system or set of file systems.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportsRegionalFileSystems
Indicates that an entity provides compatibility with or functionality for file systems specific to particular regions or locales.
-
D.
supportsBackingFiles
Indicates that an entity is capable of using or relying on underlying backing files to store or manage its data or state.
-
E.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 28, 2026, 3:24 a.m.