Triple
T3032097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPTV |
E82918
|
entity |
| Predicate | qualityDependsOn |
P45104
|
FINISHED |
| Object | network bandwidth |
—
|
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: network bandwidth | Statement: [IPTV, qualityDependsOn, network bandwidth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualityDependsOn Context triple: [IPTV, qualityDependsOn, network bandwidth]
-
A.
quality
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
-
B.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
-
C.
qualityUpdateType
Indicates the specific kind of change or modification applied to an entity’s quality or quality-related status.
-
D.
measurementDependsOn
Indicates that one measurement is derived from, influenced by, or requires another measurement in order to be defined or computed.
-
E.
accuracyDependsOn
Indicates that the accuracy of one entity or process is contingent upon, or influenced by, another entity or factor.
- F. None of above. chosen
Provenance (4 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aefc2dc8190ad9b349ca45b7e30 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.