Triple
T31583145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micro/RSX |
E805876
|
entity |
| Predicate | intendedHardwareEnvironment |
P9320
|
FINISHED |
| Object | resource-constrained PDP-11 configurations |
—
|
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: resource-constrained PDP-11 configurations | Statement: [Micro/RSX, intendedHardwareEnvironment, resource-constrained PDP-11 configurations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedHardwareEnvironment Context triple: [Micro/RSX, intendedHardwareEnvironment, resource-constrained PDP-11 configurations]
-
A.
intendedSystem
Indicates that one entity is the target or designated system for which another entity is designed, directed, or meant to operate.
-
B.
primaryOperatingEnvironment
chosen
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
-
C.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
D.
intendedEquipmentType
Indicates that a particular piece of equipment is the planned or designated type to be used in a given context or activity.
-
E.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 30, 2026, 10:24 p.m.