Triple
T33467650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCS |
E857098
|
entity |
| Predicate | supportsSubsetting |
—
|
GENERATED |
| Object | spatial subsetting |
—
|
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: supportsSubsetting Context triple: [WCS, supportsSubsetting, spatial subsetting]
-
A.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
B.
supportsSubbands
Indicates that one entity provides or is compatible with multiple subbands within a broader frequency or spectral band.
-
C.
requiresSubscript
Indicates that one element must be written with a subscript in relation to another element for proper notation or interpretation.
-
D.
coreSubset
Indicates that one set forms the essential or most important subset of another set, capturing its core elements.
-
E.
isSubscriptable
Indicates that one entity can be accessed or indexed using another entity as a subscript (e.g., via bracket notation).
- F. None of above. chosen
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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.