Triple
T28871651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Query/Retrieve Service Class |
E732158
|
entity |
| Predicate | supportsMatching |
—
|
GENERATED |
| Object | attribute-based query matching |
—
|
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: supportsMatching Context triple: [Query/Retrieve Service Class, supportsMatching, attribute-based query matching]
-
A.
supportsFinding
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
-
B.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
D.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
E.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:33 a.m.