Triple
T37442822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCSS |
E930464
|
entity |
| Predicate | hasConfigurationVariant |
—
|
GENERATED |
| Object | 4-meter DCSS |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfigurationVariant Context triple: [DCSS, hasConfigurationVariant, 4-meter DCSS]
-
A.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
hasVariantUsage
Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
-
D.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
E.
hasDistributionVariant
Indicates that one entity is a variant or alternative form of another entity specifically in terms of its distribution characteristics or pattern.
- F. None of above.
Provenance (1 batch)
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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.