Triple
T28296012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MP/M |
E713571
|
entity |
| Predicate | commandInterface |
P173242
|
FINISHED |
| Object | CP/M-like command line interface |
—
|
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: CP/M-like command line interface | Statement: [MP/M, commandInterface, CP/M-like command line interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandInterface Context triple: [MP/M, commandInterface, CP/M-like command line interface]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
-
C.
commandSyntax
Indicates the specific structure or format in which a command must be written or expressed.
-
D.
commandProcessor
Indicates that one entity is responsible for receiving, interpreting, and executing commands issued by another entity.
-
E.
interfaceConfigurationCommand
Indicates a command that configures or modifies the settings of an interface within a system or device.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 11:32 p.m.