Triple
T33467653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCS |
E857098
|
entity |
| Predicate | supportsProcessing |
P140493
|
FINISHED |
| Object | server-side coverage processing |
—
|
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: server-side coverage processing | Statement: [WCS, supportsProcessing, server-side coverage processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProcessing Context triple: [WCS, supportsProcessing, server-side coverage processing]
-
A.
supportsProcesses
chosen
Indicates that one entity provides the necessary functionality, resources, or environment for certain processes of another entity to operate or be carried out.
-
B.
supportsExceptionProcessing
Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
allowsPremiumProcessing
Indicates that one entity permits another entity to use an expedited or premium processing service for a given request or operation.
-
E.
supportsDevelopmentProcess
Indicates that one entity provides resources, tools, or assistance that facilitate or enhance another entity’s development process.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.