Triple
T33437368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetCapabilities |
E856266
|
entity |
| Predicate | serviceSectionIncludes |
P14898
|
FINISHED |
| Object | service title |
—
|
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: service title | Statement: [GetCapabilities, serviceSectionIncludes, service title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceSectionIncludes Context triple: [GetCapabilities, serviceSectionIncludes, service title]
-
A.
serviceComponentsInclude
chosen
Indicates that a service is composed of, or functionally includes, specific component elements.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
D.
servicesType
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
E.
servicesLine
Indicates that one entity provides or is associated with a particular service line or category of services for another entity.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:36 a.m.