Triple
T33437360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetCapabilities |
E856266
|
entity |
| Predicate | REQUEST |
P79829
|
FINISHED |
| Object | GetCapabilities |
—
|
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: GetCapabilities | Statement: [GetCapabilities, REQUEST, GetCapabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: REQUEST Context triple: [GetCapabilities, REQUEST, GetCapabilities]
-
A.
requestModel
Indicates that one entity asks another entity to provide or use a specific model for a task or interaction.
-
B.
requiresResponse
Indicates that an action, event, or communication necessitates a reply or follow-up response from another party.
-
C.
requestedFor
Indicates that one entity has made a request on behalf of, or targeting, another entity as the intended recipient or subject of the request.
-
D.
requestType
chosen
Indicates the specific kind or category of request being made in an interaction or transaction.
-
E.
requestsItem
Indicates that one entity asks another entity to provide or supply a specific item.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e48699808190895ab15eeb97afa6 |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.