Triple
T28998015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Virtual Storage |
E736218
|
entity |
| Predicate | notableSubsystem |
P203730
|
FINISHED |
| Object | CICS |
E207195
|
NE 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: CICS | Statement: [Multiple Virtual Storage, notableSubsystem, CICS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSubsystem Context triple: [Multiple Virtual Storage, notableSubsystem, CICS]
-
A.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
B.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
C.
notableSubzone
Indicates that a subzone is particularly significant or prominent within a larger zone or area.
-
D.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
E.
systemNotableCharacteristic
Indicates that a system possesses a particular distinguishing feature or attribute that is especially noteworthy or significant.
- F. None of above. chosen
Provenance (5 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505bc2c408190a00aa2ac202c7eeb |
completed | June 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
| PDg | Predicate description generation | batch_6a01d48e9b3481908104de8a345de5ef |
completed | May 11, 2026, 1:07 p.m. |
Created at: April 28, 2026, 9:32 a.m.