Triple
T28608632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSAM |
E724117
|
entity |
| Predicate | supportsDataSetType |
P24486
|
FINISHED |
| Object | KSDS |
—
|
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: KSDS | Statement: [VSAM, supportsDataSetType, KSDS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataSetType Context triple: [VSAM, supportsDataSetType, KSDS]
-
A.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
supportsDatastoreType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
-
C.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
D.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced 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_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: April 28, 2026, 4:29 a.m.