Triple
T33467650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCS |
E857098
|
entity |
| Predicate | supportsSubsetting |
P206480
|
FINISHED |
| Object | spatial subsetting |
—
|
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: spatial subsetting | Statement: [WCS, supportsSubsetting, spatial subsetting]
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 (4 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:37 a.m.