Triple
T7192370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPL network |
E167723
|
entity |
| Predicate | computingEnvironment |
P9320
|
FINISHED |
| Object | mainframe and minicomputer systems |
—
|
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: mainframe and minicomputer systems | Statement: [NPL network, computingEnvironment, mainframe and minicomputer systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingEnvironment Context triple: [NPL network, computingEnvironment, mainframe and minicomputer systems]
-
A.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
B.
primaryOperatingEnvironment
chosen
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
-
C.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
D.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
E.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e901ea1481908a9e44f96dd4b553 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.