Triple
T31582581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Files-11 |
E805865
|
entity |
| Predicate | variantUsedFor |
P4680
|
FINISHED |
| Object | ODS-2: standard VMS disk volumes |
—
|
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: ODS-2: standard VMS disk volumes | Statement: [Files-11, variantUsedFor, ODS-2: standard VMS disk volumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variantUsedFor Context triple: [Files-11, variantUsedFor, ODS-2: standard VMS disk volumes]
-
A.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
-
B.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
hasVariantUsage
Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
-
E.
variant
chosen
Indicates that one entity is an alternative form, version, or variation 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:24 p.m.