Triple
T28608489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Program (CP) |
E724114
|
entity |
| Predicate | supportsGuestType |
P82507
|
FINISHED |
| Object | z/OS |
—
|
NE NERFINISHED |
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: z/OS | Statement: [Control Program (CP), supportsGuestType, z/OS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGuestType Context triple: [Control Program (CP), supportsGuestType, z/OS]
-
A.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
-
B.
allowsGuests
Indicates that an entity permits other people, not part of its primary group or membership, to be present or participate.
-
C.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
D.
supportsUserType
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
-
E.
supportsGuestArchitecture
chosen
Indicates that one entity provides the necessary capabilities or environment to run or host the specified guest architecture of 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_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: April 28, 2026, 4:28 a.m.