Triple
T28296253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M Console Command Processor (8-bit CCP) |
E713578
|
entity |
| Predicate | reloadedBy |
P7738
|
FINISHED |
| Object | warm boot sequence |
—
|
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: warm boot sequence | Statement: [CP/M Console Command Processor (8-bit CCP), reloadedBy, warm boot sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reloadedBy Context triple: [CP/M Console Command Processor (8-bit CCP), reloadedBy, warm boot sequence]
-
A.
reprogrammedBy
Indicates that an entity’s original programming or code has been altered or replaced by another specified agent or process.
-
B.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
C.
revivedBy
chosen
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
D.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
E.
relocationBy
Indicates that one entity causes or performs the movement or transfer of another entity from one location to another.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644ae76e881909c12407afdbb77e4 |
completed | May 2, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:32 p.m.