Triple
T21224092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ViLTE |
E523046
|
entity |
| Predicate | qualityOfServiceMechanism |
P127932
|
FINISHED |
| Object | QoS bearer |
—
|
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: QoS bearer | Statement: [ViLTE, qualityOfServiceMechanism, QoS bearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualityOfServiceMechanism Context triple: [ViLTE, qualityOfServiceMechanism, QoS bearer]
-
A.
supportsQualityOfService
chosen
Indicates that one entity provides or enables quality-of-service guarantees or capabilities for another entity or interaction.
-
B.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
C.
qualifyingService
Indicates that an entity provides a service that meets specified criteria or standards required for a particular purpose or status.
-
D.
modeOfService
Indicates the manner, method, or channel through which a service is delivered or provided.
-
E.
congestionControlAlgorithm
Indicates that one entity uses, implements, or is associated with a particular congestion control algorithm in managing network traffic.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.