Triple
T9532708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSX-11 |
E229933
|
entity |
| Predicate | supportsUserMode |
P31535
|
FINISHED |
| Object | timesharing users |
—
|
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: timesharing users | Statement: [RSX-11, supportsUserMode, timesharing users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUserMode Context triple: [RSX-11, supportsUserMode, timesharing users]
-
A.
supportsSupervisorUserModes
Indicates that an entity provides or enables both supervisor (privileged) and user (unprivileged) operating modes.
-
B.
supportsMultiuser
chosen
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
C.
supportsUserType
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
-
D.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b5651881908241b040f123c6a8 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.