Triple
T27572740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLNS |
E696075
|
entity |
| Predicate | supportsQoSIndication |
P127932
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CLNS, supportsQoSIndication, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsQoSIndication Context triple: [CLNS, supportsQoSIndication, yes]
-
A.
supportsQualityOfService
chosen
Indicates that one entity provides or enables quality-of-service guarantees or capabilities for another entity or interaction.
-
B.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
C.
supportsAudioQuality
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
-
D.
supportsOAM
Indicates that one entity provides compatibility with, or functional backing for, the Open Application Model (OAM) in relation to another entity.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 27, 2026, 1:44 p.m.