Triple
T10330071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFS |
E242850
|
entity |
| Predicate | serviceBinding |
P28597
|
FINISHED |
| Object | KVP over HTTP GET |
—
|
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: KVP over HTTP GET | Statement: [WFS, serviceBinding, KVP over HTTP GET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBinding Context triple: [WFS, serviceBinding, KVP over HTTP GET]
-
A.
servicePatternType
Indicates the type or category of service pattern that characterizes how a service is structured, scheduled, or delivered.
-
B.
protocolBinding
chosen
Indicates that one protocol is bound or mapped to another protocol or transport mechanism for communication or interoperability purposes.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
serviceRibbon
Indicates that one entity has been awarded or is associated with a particular service ribbon in relation to another entity (such as a person, organization, or event).
-
E.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.