Triple
T28871560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Class Provider |
E732156
|
entity |
| Predicate | mustSpecify |
P134650
|
FINISHED |
| Object | supported SOP Classes |
—
|
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: supported SOP Classes | Statement: [Service Class Provider, mustSpecify, supported SOP Classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustSpecify Context triple: [Service Class Provider, mustSpecify, supported SOP Classes]
-
A.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
B.
mustBeUsed
chosen
Indicates that one entity is required or obligated to be utilized or applied in relation to another entity or context.
-
C.
mustDeclare
Indicates that one entity is required or obligated to formally state, disclose, or announce something to another entity or authority.
-
D.
mustServe
Indicates that one entity is obligated or required to provide service or perform duties for another entity.
-
E.
mustTell
Indicates that one entity is obligated or required to inform or disclose something to 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a47793481908efd891e27e541bf |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:33 a.m.