Triple
T28608660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSAM |
E724117
|
entity |
| Predicate | logicalUnit |
P93873
|
FINISHED |
| Object | control interval |
—
|
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: control interval | Statement: [VSAM, logicalUnit, control interval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalUnit Context triple: [VSAM, logicalUnit, control interval]
-
A.
isPeripheralUnitOf
Indicates that one unit functions as a subsidiary or outer component belonging to, and typically supporting, a larger central unit.
-
B.
managementUnitOf
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
-
C.
basicUnitOf
chosen
Indicates that one entity serves as the fundamental or smallest constituent unit from which the other entity is composed or defined.
-
D.
authorizedUnit
Indicates that one entity is officially permitted or empowered to act on behalf of, or perform certain actions for, another entity or system.
-
E.
operatedUnit
Indicates that one entity functions as a unit or component that is operated or controlled by 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:29 a.m.